[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110816171829.2229c18d@schatten.dmk.lab>
Date: Tue, 16 Aug 2011 17:18:29 +0200
From: Florian Mickler <florian@...kler.org>
To: Arnaud Lacombe <lacombar@...il.com>
Cc: Randy Dunlap <rdunlap@...otime.net>,
lkml <linux-kernel@...r.kernel.org>,
Mike Waychison <mikew@...gle.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>, Theodore Tso <tytso@....edu>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Documentation: add Internal-reference-ID: patch tag
On Mon, 15 Aug 2011 13:12:13 -0700
Randy Dunlap <rdunlap@...otime.net> wrote:
> On Mon, 15 Aug 2011 14:36:41 -0400 Arnaud Lacombe wrote:
>
> > Hi,
> >
> > On Fri, Jul 29, 2011 at 9:00 PM, Randy Dunlap <rdunlap@...otime.net> wrote:
> > > From: Randy Dunlap <rdunlap@...otime.net>
> > >
> > > Introduce "Internal-reference-ID:" for company-internal
> > > patch tracking. Also clarify that URLs in patches should be
> > > public, not private.
> > >
> > > Based on emails from Greg Kroah-Hartman.
> > >
> > > Internal-reference-ID: rdunlap.2011.0729.id1
> > >
> > What's the point of this for individuals ? Couldn't the Message-id
> > from the mail be re-used ?
> >
> > - Arnaud
>
> Individuals or companies might like to track their upstream patches
> easily. A pseudo-random message-id doesn't do that (for me).
Also when parsing the changelog it is nice to be able to skip those
lines by common prefix. Without prefix you can easily get
trapped by the <id-text> having similar patterns to what you look
for.
Regards,
Flo
--
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