From: "H. Peter Anvin" <hpa@zytor.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Mike Waychison <mikew@google.com>, Greg KH <gregkh@suse.de>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Theodore Tso <tytso@mit.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Documentation: add Internal-reference-ID: patch tag
Date: Sat, 13 Aug 2011 17:29:52 -0400 [thread overview]
Message-ID: <2d50505d-3500-47d8-84d4-b32850bdec7e@email.android.com> (raw)
In-Reply-To: <20110813123401.76ffcfcc.rdunlap@xenotime.net>
Randy Dunlap <rdunlap@xenotime.net> wrote:
>On Sun, 31 Jul 2011 11:09:56 -0700 H. Peter Anvin wrote:
>
>> On 07/31/2011 11:07 AM, Mike Waychison wrote:
>> >>>
>> >>> Internal-reference-ID: rdunlap.2011.0729.id1
>> >>>
>> >
>> > Acked-by: Mike Waychison <mikew@google.com>
>> >
>>
>> Just to avoid namespace collisions, can we at least put the owner
>> somewhere standardized, e.g. <2011.0729.id1@rdunlap>, <33999@google>
>and
>> so on?
>
>I would prefer to leave the text contents as unspecified, but I
>wouldn't
>mind recommending that users try to make them unique, e.g., by using
>a company-ID or owner-ID. Would that be acceptable?
>
>
>---
>~Randy
>*** Remember to use Documentation/SubmitChecklist when testing your
>code ***
No, that wouldn't work when there is more than one tag from different users. And yes, I fully expect to see that.
--
Sent from my mobile phone. Please excuse my brevity and lack of formatting.
next prev parent reply other threads:[~2011-08-13 21:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 1:00 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 [this message]
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
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=2d50505d-3500-47d8-84d4-b32850bdec7e@email.android.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome