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 06:27:36 +0200 [thread overview]
Message-ID: <20060731042736.GA10597@mars.ravnborg.org> (raw)
In-Reply-To: <20060730.155956.106769160.davem@davemloft.net>
On Sun, Jul 30, 2006 at 03:59:56PM -0700, David Miller wrote:
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Mon, 31 Jul 2006 00:45:43 +0200
>
> > >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
> > --------------
>
> The patch format specifies things that make no sense
> when the changes gets into the tree. Especially the
> sequence numbers, which are implied by the changes
> placement in the relative changeset history.
"git am" removes the patch format specifiers when the change are
committed. git applymbox replace the patch format specifier with
[PATCH].
So:
git am => subsystem: summary phrase
git applymbox => [PATCH] subsystem: summary phrase
Both variants exists because Linus uses the latter to distingush between
what is applied via git tress and what is applied via mail patches.
The Signed-off-by: carries same info btw.
Sam
prev parent reply other threads:[~2006-07-31 4:27 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
2006-07-30 22:59 ` David Miller
2006-07-31 4:27 ` Sam Ravnborg [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=20060731042736.GA10597@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).