From: Chris Metcalf <cmetcalf@ezchip.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
Gilad Ben Yossef <giladb@ezchip.com>,
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 v2] Documentation/SubmittingPatches: discuss In-Reply-To
Date: Wed, 11 Nov 2015 13:35:10 -0500 [thread overview]
Message-ID: <56438A5E.9040800@ezchip.com> (raw)
In-Reply-To: <20151111100711.396d1d7b@xps>
On 11/11/2015 12:07 PM, Jonathan Corbet wrote:
> On Thu, 5 Nov 2015 15:21:47 -0500
> Chris Metcalf <cmetcalf@ezchip.com> wrote:
>
>> Add a paragraph suggesting best practices for when to link patches
>> to previous LKML messages via In-Reply-To.
> We're getting there, but in the middle of the discussion on the format of
> the patch itself seems like the wrong place. So I've applied this, but I
> took the liberty of moving the new paragraph into its own section.
Great, thanks!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
prev parent reply other threads:[~2015-11-11 18:35 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
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 [this message]
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=56438A5E.9040800@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.