From: Jonathan Corbet <corbet@lwn.net>
To: Chris Metcalf <cmetcalf@ezchip.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Gilad Ben Yossef <giladb@ezchip.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Tejun Heo <tj@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Andy Lutomirski <luto@amacapital.net>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation/email-clients.txt: discuss In-Reply-To
Date: Thu, 5 Nov 2015 11:31:05 -0700 [thread overview]
Message-ID: <20151105113105.502021b4@lwn.net> (raw)
In-Reply-To: <1445616781-8212-1-git-send-email-cmetcalf@ezchip.com>
On Fri, 23 Oct 2015 12:13:01 -0400
Chris Metcalf <cmetcalf@ezchip.com> wrote:
> +When manually adding In-Reply-To: headers to a patch (e.g., using `git
> +send email`), use common sense to associate the patch with previous
> +relevant discussion, e.g. link a bug fix to the email with the bug report.
> +For a multi-patch series, it is generally best to avoid using
> +In-Reply-To: to link to older versions of the series. This way
> +multiple versions of the patch don't become an unmanageable forest of
> +references in email clients. If a link is helpful, you can use an
> +"http://lkml.kernel.org/r/MESSAGEID" URL (e.g., in the cover email
> +text) to link to an earlier version of the patch series.
So this is sitting in my docs folder waiting to see if anybody else had
anything to say. Nope. I guess I'm not opposed to this addition, but
I'm not quite sure what problem is being solved. Is there a plague of
inappropriate hand-crafted In-Reply-To headers out there that I've not
seen?
Beyond that, this seems like advice that is better put into
SubmittingPatches if we really want it.
Thanks,
jon
next prev parent reply other threads:[~2015-11-05 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 16:13 [PATCH] Documentation/email-clients.txt: discuss In-Reply-To Chris Metcalf
2015-11-05 18:31 ` Jonathan Corbet [this message]
2015-11-05 19:11 ` Chris Metcalf
2015-11-05 19:23 ` Steven Rostedt
2015-11-05 20:21 ` [PATCH v2] Documentation/SubmittingPatches: " Chris Metcalf
2015-11-06 13:57 ` Frederic Weisbecker
2015-11-11 17:07 ` Jonathan Corbet
2015-11-11 18:35 ` Chris Metcalf
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=20151105113105.502021b4@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=fweisbec@gmail.com \
--cc=giladb@ezchip.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.com \
/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