From: Florian Mickler <florian@mickler.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>,
Mike Waychison <mikew@google.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Theodore Tso <tytso@mit.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Documentation: add Internal-reference-ID: patch tag
Date: Tue, 16 Aug 2011 17:18:29 +0200 [thread overview]
Message-ID: <20110816171829.2229c18d@schatten.dmk.lab> (raw)
In-Reply-To: <20110815131213.c66a9e61.rdunlap@xenotime.net>
On Mon, 15 Aug 2011 13:12:13 -0700
Randy Dunlap <rdunlap@xenotime.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@xenotime.net> wrote:
> > > From: Randy Dunlap <rdunlap@xenotime.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
prev parent reply other threads:[~2011-08-16 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 1:00 [PATCH] Documentation: add Internal-reference-ID: patch tag Randy Dunlap
2011-07-30 23:56 ` Greg KH
2011-07-31 18:07 ` Mike Waychison
2011-07-31 18:09 ` H. Peter Anvin
2011-08-13 19:34 ` Randy Dunlap
2011-08-13 21:29 ` H. Peter Anvin
2011-08-15 3:23 ` Randy Dunlap
2011-08-15 5:19 ` H. Peter Anvin
2011-08-15 17:39 ` Mike Waychison
2011-08-15 18:27 ` H. Peter Anvin
2011-08-15 20:23 ` Randy Dunlap
2011-08-15 20:47 ` H. Peter Anvin
2011-08-15 21:00 ` Randy Dunlap
2011-08-15 22:12 ` H. Peter Anvin
2011-08-15 18:36 ` Arnaud Lacombe
2011-08-15 20:12 ` Randy Dunlap
2011-08-16 15:18 ` Florian Mickler [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=20110816171829.2229c18d@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=rdunlap@xenotime.net \
--cc=tytso@mit.edu \
/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.