[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090424132655.GA4132@windriver.com>
Date: Fri, 24 Apr 2009 09:26:55 -0400
From: Paul Gortmaker <paul.gortmaker@...driver.com>
To: Jonathan Corbet <corbet@....net>
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
[Re: [PATCH] documentation: list common guidelines for commit log content] On 23/04/2009 (Thu 17:08) Jonathan Corbet wrote:
> 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.
Fine by me. I agree that not everything can live in the kernel, and
long lists can test the limits of a person's attention span. I've
found value in using such a list internally, so thought it worth
sharing. If nothing else, people can reference the list via a mailing
list archive or similar now.
Paul.
>
> 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/
Powered by blists - more mailing lists