linux-kernel - Re: [patch 1/1] document Acked-by:

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]

Date:	Fri, 01 Jun 2007 21:27:05 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Valdis.Kletnieks@...edu,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 1/1] document Acked-by:

"John Anthony Kazos Jr." <jakj@...-k-j.com> writes:

> Indeed. Acked-by: implies authority, and only very few people should be 
> able to do it. Namely, the only person who can ACK a patch is a person who 
> could also NACK a patch and expect it to actually be dropped. If I think a 
> patch is bad, I can say so, but as I have no authority, my statement would 
> be taken on merit alone, whereas Linus or Andrew or such could just NACK 
> it and move on without having to spew a blurb every time.

Everyone always has some authority so everyone can ack or nack any
patch and I hope the action taken will always depend on merit
rather than person, especially if it's a technical issue and not
some style etc. thing.
-- 
Krzysztof Halasa
-
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/