linux-kernel - Re: [PATCH, RFC] A development process document

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] [day] [month] [year] [list]

Date:	Fri, 1 Aug 2008 12:52:48 -0400 (EDT)
From:	Daniel Barkalow <barkalow@...ervon.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	"Randy.Dunlap" <rdunlap@...otime.net>,
	Jonathan Corbet <corbet@....net>, Alex Chiang <achiang@...com>,
	LKML <linux-kernel@...r.kernel.org>,
	Amanda McPherson <amanda@...pherson.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH, RFC] A development process document

On Fri, 1 Aug 2008, Stefan Richter wrote:

> Randy.Dunlap wrote:
>
> > but.. but Andrew often has to take part(s) of #0/N and add them to the
> > changelog(s) to make the changelog(s) meaningful.  I.e., someone skimped
> > on what should have been in the changelog(s).
> 
> That would not be a problem with the cover posting, it would be a
> problem with the changelogs.  The same applies if the respective
> information is put below the '---' delimiter line in the individual
> patch postings. 

Or, for that matter, left out entirely. Or in the first actual patch of 
the series, since people will often be looking through the log filtered in 
some way, or bisect or blame will take them to the middle of the series.

> So just remember that changelogs need to be sufficiently comprehensive 
> even when read standalone, out of the context of the series.

I think this would be a good statement to include in the section about 
changelogs.

	-Daniel
*This .sig left intentionally blank*
--
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/