| 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
| ||
|
Message-ID: <m3ps4dubru.fsf@maximus.localdomain> Date: Sun, 03 Jun 2007 02:23:01 +0200 From: Krzysztof Halasa <khc@...waw.pl> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org Subject: Re: [patch 1/1] document Acked-by: Andrew Morton <akpm@...ux-foundation.org> writes: > I do that often. It's useful information. If person X sends an fbdev > patch and Tony says "whoa, neat" and I send the patch to Linus then > Linus could > well think "wtf, Andrew doesn't know anything about fbdev". So I do s/whoa > neat/Acked-by:/ to tell the world that someone who knows something has > looked at the change. Makes sense. > +Acked-by: does not necessarily indicate acknowledgement of the entire patch. > +For example, if a patch affects multiple subsystems and has an Acked-by: from > +one subsystem maintainer then this usually indicates acknowledgement of just > +the part which affects that maintainer's code. I'd add, just to be explicit, that acked-by does not necessarily mean the acker is a maintainer of any subsystem the patch touches, or generally maintainer of any code. Unless it isn't true, of course, i.e., unless we really want to limit expressing non-maintainers opinion in form of ack and nak. -- 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/
Powered by blists - more mailing lists