From: Karel Zak <kzak@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Patch format in ext4 patch queue.
Date: Mon, 24 Sep 2007 23:34:06 +0200 [thread overview]
Message-ID: <20070924213406.GF4568@petra.dvoda.cz> (raw)
In-Reply-To: <46F39DF6.30402@linux.vnet.ibm.com>
On Fri, Sep 21, 2007 at 04:03:26PM +0530, Aneesh Kumar K.V wrote:
> First line should be
> <subsystem_name>: A single line description of the patch.
> This appear in the subject line of the mail that results from different
> commit list.
BTW, we use this subject format for util-linux-ng and I have a simple
python script that generates nice changelogs (for release notes) from
git log.
IMHO a changelog [1] that is sorted and grouped by <subsystem_name>
is better for end-users that output from git-shortlog.
Karel
[1] see Changelog section:
ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.13/v2.13-ReleaseNotes
--
Karel Zak <kzak@redhat.com>
prev parent reply other threads:[~2007-09-24 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 10:33 Patch format in ext4 patch queue Aneesh Kumar K.V
2007-09-21 11:24 ` Aneesh Kumar K.V
2007-09-21 11:46 ` Theodore Tso
2007-09-24 21:34 ` Karel Zak [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=20070924213406.GF4568@petra.dvoda.cz \
--to=kzak@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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