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: Mon, 15 Aug 2011 13:47:23 -0700 [thread overview]
Message-ID: <4E4985DB.20109@zytor.com> (raw)
In-Reply-To: <20110815132331.74cd0484.rdunlap@xenotime.net>
On 08/15/2011 01:23 PM, Randy Dunlap wrote:
> On Mon, 15 Aug 2011 11:27:53 -0700 H. Peter Anvin wrote:
>
>> On 08/15/2011 10:39 AM, Mike Waychison wrote:
>>>>
>>>> I would like to see the <id@owner> format I mentioned.
>>>
>>> Is there a middle ground if we say:
>>>
>>> Internal-reference-ID: <arbitrarytextforid@owner>
>>>
>>> so
>>>
>>> Internal-reference-ID: <2011.0729.id1@rdunlap>
>>> Internal-reference-ID: <bug-45322143@google>
>>>
>>
>> Personally I don't care if they are separate lines or all on the same line.
>
> I don't understand how that answers Mike's question...
>
Then I don't understand the question.
I proposed:
Internal-reference-ID: <2011.0729.id1@rdunlap> <33999@google>
Mike proposed:
Internal-reference-ID: <2011.0729.id1@rdunlap>
Internal-reference-ID: <bug-45322143@google>
The only difference I see is if they are on the same line, which I don't
personally care about.
-hpa
next prev parent reply other threads:[~2011-08-15 20:47 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 [this message]
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=4E4985DB.20109@zytor.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 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.