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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120723113449.GD9103@khazad-dum.debian.net>
Date:	Mon, 23 Jul 2012 08:34:49 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	"Du, ChangbinX" <changbinx.du@...el.com>
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?

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.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/