linux-kernel - Re: Changelog quality

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]

Date:	Fri, 15 Jan 2010 10:17:08 +0100 (CET)
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

On 15 Jan, David Miller wrote:
> What button do I push in gitk when viewing a commit to find the
> script?
> 
> If I have to go out of the tool, that's the beginning down the long
> road of potential distractions.

[There is a button in gitk which launches coccinelle and feeds the
copy-an-paste buffer into it?]

So somebody scripted a test which finds a certain type of problem, ran
it on the tree, and submitted fixes.  Later on, somebody wants to re-run
the test to check whether this problem was reintroduced in new code.  So
you are arguing that this somebody should, among else, find one of the
parts required for the test in the kernel source repository's changelog
metadata when he is in the process to add that test to his toolkit.

I on the other hold the opinion that the changelog has one purpose, to
describe the code change.
-- 
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/