From: Theodore Tso <tytso@mit.edu>
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: Fri, 21 Sep 2007 07:46:36 -0400 [thread overview]
Message-ID: <20070921114636.GN30221@thunk.org> (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:
>
> I was looking at the patch queue and see patches with different formats.
> If we can standardize on what rest of the linux kernel follows it would
> be nice.
>
> 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....
Yes, please!!! Otherwise I end up having to fix up the patch tree
before I can suck it into git.
- Ted
next prev parent reply other threads:[~2007-09-21 11:46 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 [this message]
2007-09-24 21:34 ` Karel Zak
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=20070921114636.GN30221@thunk.org \
--to=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.