| 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
| ||
|
Date: Fri, 15 Jan 2010 09:50:51 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: David Miller <davem@...emloft.net> CC: adi@...apodia.org, julia@...u.dk, nm127@...email.hu, david.vrabel@....com, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org, cocci@...u.dk Subject: Re: Changelog quality David Miller wrote: > And likewise here, I want to see what the hell found the bug by > reading the changelog message. Coccinelle found it. In contrast to parsers like sparse, it had to be programmed to do so. If you want to repeat that process, you have to get coccinelle and the script. Both can be found quickly without having them both in the SCM. > I want more information in changelog messages, not less. A commit > log message is never too long and never gives too much information > about the change, ever... If the changelog carries a lot of unimportant or even unrelated information, then only a careful structure of the text can prevent that the important information is buried in noise, and thus lost. (Julia's logs are structured respectively, so this is OK.) -- Stefan Richter -=====-==-=- ---= -==== http://arcgraph.de/sr/ -- 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