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: <2d50505d-3500-47d8-84d4-b32850bdec7e@email.android.com>
Date:	Sat, 13 Aug 2011 17:29:52 -0400
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

Randy Dunlap <rdunlap@...otime.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@...gle.com>
>> > 
>> 
>> 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 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.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ