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]
Message-ID: <84144f021001150149u3b784d26g1822be6c5c3ecbf@mail.gmail.com>
Date:	Fri, 15 Jan 2010 11:49:08 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Julia Lawall <julia@...u.dk>
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>
Subject: Re: Changelog quality

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?

                        Pekka
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ