linux-kernel - Re: [PATCH v2] Documentation/SubmittingPatches: discuss In-Reply-To

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20151106135713.GA14071@lerouge>
Date:	Fri, 6 Nov 2015 14:57:14 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Chris Metcalf <cmetcalf@...hip.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Jonathan Corbet <corbet@....net>,
	Peter Zijlstra <peterz@...radead.org>,
	Gilad Ben Yossef <giladb@...hip.com>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>, Tejun Heo <tj@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Christoph Lameter <cl@...ux.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Andy Lutomirski <luto@...capital.net>,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH v2] Documentation/SubmittingPatches: discuss In-Reply-To

On Thu, Nov 05, 2015 at 03:21:47PM -0500, Chris Metcalf wrote:
> Add a paragraph suggesting best practices for when to link patches
> to previous LKML messages via In-Reply-To.
> 
> Signed-off-by: Chris Metcalf <cmetcalf@...hip.com>

ACK!

Thanks!

> ---
>  Documentation/SubmittingPatches | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index fd89b04d34f0..9f61620f34ef 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -675,6 +675,16 @@ A couple of example Subjects:
>      Subject: [patch 2/5] ext2: improve scalability of bitmap searching
>      Subject: [PATCHv2 001/207] x86: fix eflags tracking
>  
> +It can be helpful to manually add In-Reply-To: headers to a patch
> +(e.g., when using "git send email") to associate the patch with
> +previous relevant discussion, e.g. to link a bug fix to the email with
> +the bug report.  However, 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 the https://lkml.kernel.org/ redirector (e.g., in
> +the cover email text) to link to an earlier version of the patch series.
> +
>  The "from" line must be the very first line in the message body,
>  and has the form:
>  
> -- 
> 2.1.2
> 
--
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/