From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, tytso@mit.edu
Subject: Re: [PATCH] documentation: list common guidelines for commit log content
Date: Fri, 24 Apr 2009 09:26:55 -0400 [thread overview]
Message-ID: <20090424132655.GA4132@windriver.com> (raw)
In-Reply-To: <20090423170827.47618b4e@bike.lwn.net>
[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@windriver.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
prev parent reply other threads:[~2009-04-24 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 19:00 [PATCH] documentation: list common guidelines for commit log content Paul Gortmaker
2009-04-23 23:08 ` Jonathan Corbet
2009-04-24 13:26 ` Paul Gortmaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090424132655.GA4132@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox