linux-kernel - Re: RFC: reviewer's statement of oversight

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.64.0710081939120.10239@fbirervta.pbzchgretzou.qr>
Date:	Mon, 8 Oct 2007 19:45:27 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	Jonathan Corbet <corbet@....net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: RFC: reviewer's statement of oversight

On Oct 8 2007 19:37, Sam Ravnborg wrote:
>snip...
>
>Or maybe we need something much less formal that explain the purpose of the
>four tags we use:

At least formal try:

>Signed-of-by:

* Used by original submitter(s).
* Also used by maintainers to track the patch's path
  (ATM, does not imply "I have look at it in depth")

>Acked-by:
>Tested-by:

* Used by random people to express their (dis)like/experience with the 
patch.

>Reviewed-by:

* I am maintaner or an 'important' person and have had a
  look at it in depth

>Cc:

* Used by original submitter to denote additional maintainers it goes to
* Parties who should be Cced when an a posteriori question comes up

My 2¥.
Jan
-
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/