From: Randy Dunlap <rdunlap@xenotime.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Du, ChangbinX" <changbinx.du@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Do need keep mail in thread when sending a new version patch?
Date: Mon, 23 Jul 2012 13:43:03 -0700 [thread overview]
Message-ID: <500DB757.2030200@xenotime.net> (raw)
In-Reply-To: <20120723184349.GB22968@khazad-dum.debian.net>
On 07/23/2012 11:43 AM, Henrique de Moraes Holschuh wrote:
> On Mon, 23 Jul 2012, Randy Dunlap wrote:
>> On 07/23/2012 04:34 AM, Henrique de Moraes Holschuh wrote:
>>> On Mon, 23 Jul 2012, Du, ChangbinX wrote:
>>>> Hi, developers!
>>>> I have a question about sending patch: If my patch have a new version,
>>>> do I need set "--in-reply-to" option so keep them in the same thread when
>>>> sending it? And in which cases should "--in-reply-to" option be set? Thanks!
>>>
>>> Yes, please do it when possible. It groups patches nicely in theaded email
>>> readers, and it makes it easier for people who are interested in the subject
>>> to find the new version of your patchset (and all individual patches that
>>> are part of the same patchset), AND for people who are not interested to
>>> skip the entire thing.
>>
>>
>> Please compare to a proposed patch:
>>
>> http://marc.info/?l=linux-doc&m=133539116205348&w=2
>
> This one (referenced by the commit changelog of the above) seems to be a
> better explanation:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-April/096236.html
>
> Anyway, I stand corrected.
>
Well, that patch isn't merged into mainline yet, right?
and it is only one opinion.
I don't mind seeing the new versions of a patch sent as
replies to older versions, so I don't see a need to codify it.
--
~Randy
next prev parent reply other threads:[~2012-07-23 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 5:53 Do need keep mail in thread when sending a new version patch? Du, ChangbinX
2012-07-23 11:34 ` Henrique de Moraes Holschuh
2012-07-23 17:28 ` Randy Dunlap
2012-07-23 18:43 ` Henrique de Moraes Holschuh
2012-07-23 20:43 ` Randy Dunlap [this message]
2012-07-24 1:57 ` Du, ChangbinX
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=500DB757.2030200@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=changbinx.du@intel.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
/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