From: Sam Ravnborg <sam@ravnborg.org>
To: David Miller <davem@davemloft.net>
Cc: ilpo.jarvinen@helsinki.fi, netdev@vger.kernel.org
Subject: Re: Subsystem/prefix in patch submission format
Date: Mon, 31 Jul 2006 00:45:43 +0200 [thread overview]
Message-ID: <20060730224543.GA9506@mars.ravnborg.org> (raw)
In-Reply-To: <20060730.152846.42906358.davem@davemloft.net>
On Sun, Jul 30, 2006 at 03:28:46PM -0700, David Miller wrote:
> From: "Ilpo J?rvinen" <ilpo.jarvinen@helsinki.fi>
> Date: Sun, 30 Jul 2006 14:01:09 +0300 (EEST)
>
> > [TCP] FRTO: summary here
>
> This looks perfectly fine.
Looking 100 commits back or so it is obvious we have two distinct
notations:
subsystem: <what was changed>
and
[subsystem] <what was changed>
net related stuff counts for most of the latter but it is used in
several other places.
>From a pure eye-candy perspective it would be nice to use same format
all over.
>From Documentation/SubmittingPatches:
------------------
12) The canonical patch format
The canonical patch subject line is:
Subject: [PATCH 001/123] subsystem: summary phrase
--------------
Sam
next prev parent reply other threads:[~2006-07-30 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 11:01 Subsystem/prefix in patch submission format Ilpo Järvinen
2006-07-30 22:28 ` David Miller
2006-07-30 22:45 ` Sam Ravnborg [this message]
2006-07-30 22:59 ` David Miller
2006-07-31 4:27 ` Sam Ravnborg
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=20060730224543.GA9506@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).