linux-kernel - RE: Do need keep mail in thread when sending a new version patch?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0C18FE92A7765D4EB9EE5D38D86A563A0B3029@SHSMSX101.ccr.corp.intel.com>
Date:	Tue, 24 Jul 2012 01:57:06 +0000
From:	"Du, ChangbinX" <changbinx.du@...el.com>
To:	Randy Dunlap <rdunlap@...otime.net>,
	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Do need keep mail in thread when sending a new version patch?

Thank you all. Maybe both of the two ideas are acceptable.
Seeing your discussion, I prefer to group patches in thread if thread is
not heavy, else I would like to start a new thread.

Thanks again.
Du, Changbin

> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@...otime.net]
> Sent: Tuesday, July 24, 2012 4:43 AM
> To: Henrique de Moraes Holschuh
> Cc: Du, ChangbinX; linux-kernel@...r.kernel.org
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/