Messages in this thread | | | Date | Mon, 23 Jul 2012 13:43:03 -0700 | From | Randy Dunlap <> | Subject | Re: Do need keep mail in thread when sending a new version patch? |
| |
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
| |