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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 15 Jan 2010 00:24:24 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	stefanr@...6.in-berlin.de
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

From: Stefan Richter <stefanr@...6.in-berlin.de>
Date: Fri, 15 Jan 2010 09:13:26 +0100

> Tell me again in what way the script is of any importance or of any help
> in the permanent SCM changelog after commit.

I find them extremely useful when going through old as well
as new changes.

> I agree with you that it is very good to have the script in the patch
> posting, but I disagree about the changelog.

Thanks for making me go comb the mailing list archives instead of
having the information readily available when looking at a change in
the git history.

I frankly think all of your objections to this kind of thing as well
as putting patchwork URLs into the MAINTAINERS file quite rediculious.

Putting something 100 times (or more) into the kernel tree
documentation or commit messages is a good thing, because people are
going to find the information they need faster.

And likewise here, I want to see what the hell found the bug by
reading the changelog message.

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...
--
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/