From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: siddhesh@redhat.com, libc-alpha@sourceware.org,
goldstein.w.n@gmail.com, Wilco.Dijkstra@arm.com
Subject: Re: Why did one of Wilco's patches land into an untitled series?
Date: Mon, 06 Feb 2023 15:46:35 -0500 [thread overview]
Message-ID: <xnfsbicyj8.fsf@greed.delorie.com> (raw)
In-Reply-To: <3cf074ef-7121-e4bd-97d0-12bf8d1de7c6@redhat.com>
> Subject: [PATCH v12 12/31] string: Improve generic strnlen with memchr
> From: Wilco Dijkstra via Libc-alpha <libc-alpha@sourceware.org>
> Reply-To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
No "Re:", not a reply.
Patchwork seems to rely on the "Re:" in the subject...
* you need to remove the Re: if you're sending a v2 or it shows up as a
review of v1.
* apparently if you accidentally omit the Re: it becomes a new series if
it even remotely includes a patch of some sort.
prev parent reply other threads:[~2023-02-06 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 15:56 Carlos O'Donell
2023-02-06 20:46 ` DJ Delorie [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xnfsbicyj8.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=carlos@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@redhat.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.
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).