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 11:05:21 +0100 (CET)
From:	Julia Lawall <julia@...u.dk>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	David Miller <davem@...emloft.net>, stefanr@...6.in-berlin.de,
	adi@...apodia.org, nm127@...email.hu, david.vrabel@....com,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	cocci@...u.dk, Andrew Morton <akpm@...ux-foundation.org>,
	Nicolas Palix <npalix@...u.dk>
Subject: Re: Changelog quality

On Fri, 15 Jan 2010, Pekka Enberg wrote:

> Hi Julia,
> 
> On Fri, Jan 15, 2010 at 11:43 AM, Julia Lawall <julia@...u.dk> wrote:
> >> If you want more clear markers around the script so you can skim
> >> past it more efficiently when reading the commit message, then ask
> >> for that.
> >
> > If there were markers that would cause tools to hide some information
> > under a +, that would be great.  Sometimes I have simplified a script
> > beyond what would really be reusable just to not create an over-large
> > changelog.  I hope that the simplified version is at least understandable,
> > so that the reader can get an idea of what considerations went into the
> > change, but I recall in one case having messed up on that as well, and
> > ended up with something that really gave no information whatsoever.
> 
> It seems to me that the scripts are kernel specific so why don't we
> put those useful scripts _within_ the kernel source tree and introduce
> a "make coccinelle-check" target?

Indeed, perhaps a solution that would satisfy everyone would be to make a 
place for scripts, perhaps with subdirectories for various tools, and then 
when one submits a patch for tool X, one could then submit the script at 
the same time (if it wasn't there already) and just refer to the script 
that was used.  That way, if someone wants to know more about how the 
change was made, they could look up the information, and if one does not, 
then one would not be bother by having to scroll down to see the actual 
patch.

julia