From: Attila Lendvai <attila@lendvai.name>
To: "reza.housseini@gmail.com" <reza.housseini@gmail.com>
Cc: Christopher Baines <mail@cbaines.net>,
guix-devel@gnu.org, 66262@debbugs.gnu.org
Subject: Re: Failed to build in QA
Date: Wed, 29 Nov 2023 19:54:48 +0000 [thread overview]
Message-ID: <xwNeT6gUzeFCqfOOAg53EInzT5z7xQjDmgAGLj0krB6NsrtlH_SoqmcHO89p9ACLbrX2cBsVSew0AZHGPjhsZQ7u4EMUPyOsmif21Bbs2dU=@lendvai.name> (raw)
In-Reply-To: <5B2CC699-5047-4F0C-9245-985BE9AA82B8@gmail.com>
> > The other issue with the v4 series is that Patchwork has got confused
> > and only picked out the first of the v4 patches. The threading also
> > looks weird to me in my email client, but I'm not quite sure why. How
> > did you send the v4 patches?
>
>
> I sent them with git send-mail but I also noticed that the order got
> mixed up in issues.guix.gnu.org, no idea how this happened...
i also see this every once in a while. i guess it's because the SMTP server-farm receives mutliple emails in close proximity, and they end up reaching debbugs in a different order.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“In matters of conscience, the law of majority has no place.”
— Mahatma Gandhi (1869–1948)
prev parent reply other threads:[~2023-11-29 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 7:43 Failed to build in QA reza.housseini
2023-10-05 8:49 ` Christopher Baines
2023-10-05 10:59 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-10-06 5:49 ` reza.housseini
2023-10-06 12:14 ` [bug#66262] " Christopher Baines
2023-10-09 12:40 ` Reza Housseini
2023-10-09 12:40 ` [bug#66262] " Reza Housseini
2023-10-10 17:09 ` Christopher Baines
2023-10-20 7:57 ` reza.housseini
2023-10-20 7:57 ` [bug#66262] " reza.housseini
2023-11-29 14:49 ` Reza Housseini
2023-11-29 14:49 ` [bug#66262] " Reza Housseini
2023-11-29 16:06 ` Christopher Baines
2023-11-29 16:35 ` reza.housseini
2023-11-29 19:54 ` Attila Lendvai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='xwNeT6gUzeFCqfOOAg53EInzT5z7xQjDmgAGLj0krB6NsrtlH_SoqmcHO89p9ACLbrX2cBsVSew0AZHGPjhsZQ7u4EMUPyOsmif21Bbs2dU=@lendvai.name' \
--to=attila@lendvai.name \
--cc=66262@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=reza.housseini@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).