public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Du, ChangbinX" <changbinx.du@intel.com>
Cc: "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 08:34:49 -0300	[thread overview]
Message-ID: <20120723113449.GD9103@khazad-dum.debian.net> (raw)
In-Reply-To: <0C18FE92A7765D4EB9EE5D38D86A563A0B2DCF@SHSMSX101.ccr.corp.intel.com>

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

  reply	other threads:[~2012-07-23 11:34 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 [this message]
2012-07-23 17:28   ` Randy Dunlap
2012-07-23 18:43     ` Henrique de Moraes Holschuh
2012-07-23 20:43       ` Randy Dunlap
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=20120723113449.GD9103@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=changbinx.du@intel.com \
    --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