[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1001131301180.3518-100000@iolanthe.rowland.org>
Date: Wed, 13 Jan 2010 13:04:52 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Greg KH <greg@...ah.com>
cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Julia Lawall <julia@...u.dk>,
N?meth M?rton <nm127@...email.hu>,
David Vrabel <david.vrabel@....com>,
<linux-usb@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
<cocci@...u.dk>
Subject: Re: Changelog quality
On Wed, 13 Jan 2010, Greg KH wrote:
> > It would be nice if there was a way to link automatically a git commit
> > to an archived copy of the email message in which it was originally
> > submitted.
>
> Ingo has been doing this on some patches by putting a message-id field
> in the signed-off-by area showing what lkml message a patch came from.
>
> See git commit id 6432e734c99ed685e3cad72f7dcae4c65008fcab in Linus's
> tree as an example of this.
>
> I have no objection if people want to do this for any patches going
> through my tree as well.
If it has to be included manually by the patch submitter then it isn't
automatic. Not to mention that the submitter would need to know the
email's message-id before the email message was sent!
Something like this should belong in a maintainer's script.
Alan Stern
--
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/
Powered by blists - more mailing lists