linux-kernel - Re: [PATCH] Documentation: add Internal-reference-ID: patch tag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E4999EA.5060603@zytor.com>
Date:	Mon, 15 Aug 2011 15:12:58 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Randy Dunlap <rdunlap@...otime.net>
CC:	Mike Waychison <mikew@...gle.com>, Greg KH <gregkh@...e.de>,
	lkml <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Documentation: add Internal-reference-ID: patch tag

On 08/15/2011 02:00 PM, Randy Dunlap wrote:
> 
> You said (on July-31):
> "Just to avoid namespace collisions, can we at least put the owner
> somewhere standardized, e.g. <2011.0729.id1@...nlap>, <33999@...gle> and
> so on?"
> 
> I read that as 2 different patches & 2 different IDs, but this more
> recent line:
>> Internal-reference-ID: <2011.0729.id1@...nlap> <33999@...gle>
> 
> would be for one patch with multiple IDs.
> 
>> Mike proposed:
>>
>> Internal-reference-ID: <2011.0729.id1@...nlap>
>> Internal-reference-ID: <bug-45322143@...gle>
> 
> I think that Mike was just giving 2 examples (for 2 patches).  His proposal
> was simply for:
> Internal-reference-ID: <arbitrarytextforid@...er>
> 
> which matches your request fairly well AFAICT.
> 

Yes, that was my request.  But I also do observe that a single patch can
be tracked in multiple internal databases; for example, if
(hypothetically) Red Hat reports a bug to Google which ends up being
tracked in both bug databases, they may both want to tag the same patch.

> But if we are changing things, I think I prefer your other suggestion
> for the ID tag:  "Patch-ID".  I like it because it's shorter and
> easier to type.  :)

Agreed.

	-hpa

--
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/