linux-kernel - Re: [PATCH] documentation: list common guidelines for commit log content

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: <20090423170827.47618b4e@bike.lwn.net>
Date:	Thu, 23 Apr 2009 17:08:27 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, tytso@....edu
Subject: Re: [PATCH] documentation: list common guidelines for commit log
 content

On Thu, 16 Apr 2009 15:00:56 -0400
Paul Gortmaker <paul.gortmaker@...driver.com> wrote:

> Recent discussions on lkml have brought to light that it is
> probably worthwhile documenting some of the common (yet up to
> now implicit) requirements that exist for commit log content.
> This is by no means exhaustive, but it is a start.

Sorry I sat on this for a week; I've not ignored it.

The change made me uncomfortable, despite the fact that I didn't really
disagree with anything in it.  I guess I feel that there's only so far
that it makes sense to go with big long lists of do's and don't's.
That document is plenty long already...  So I put together something
shorter which tries to focus on the problem at a higher level.  

But maybe others disagree?

Thanks,

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