From: Sam Ravnborg <sam@ravnborg.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Nick Piggin <npiggin@kernel.dk>
Subject: Re: [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP
Date: Sat, 21 Aug 2010 22:05:28 +0200 [thread overview]
Message-ID: <20100821200528.GA27421@merkur.ravnborg.org> (raw)
In-Reply-To: <20100821195559.GC4760@const.famille.thibault.fr>
>
> Ah, I didn't realize you scripts include the subject topic too. Maybe it
> should be said in SubmittingPatches that the "summary phrase" shouldn't
> be repeated in the body.
>From said document:
15) The canonical patch format
The canonical patch subject line is:
Subject: [PATCH 001/123] subsystem: summary phrase
The canonical patch message body contains the following:
- A "from" line specifying the patch author.
- An empty line.
- The body of the explanation, which will be copied to the
permanent changelog to describe this patch.
- The "Signed-off-by:" lines, described above, which will
also go in the changelog.
- A marker line containing simply "---".
- Any additional comments not suitable for the changelog.
- The actual patch (diff output).
That should do it. We cannot tell what should NOT be done.
If you use git then it is trivial to commit your changes and
generate patches using "git format-patch ..."
Sam
next prev parent reply other threads:[~2010-08-21 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 19:32 Samuel Thibault
2010-08-21 19:45 ` Linus Torvalds
2010-08-21 19:55 ` Samuel Thibault
2010-08-21 20:05 ` Sam Ravnborg [this message]
2010-08-21 20:10 ` Samuel Thibault
2010-08-21 20:16 ` Linus Torvalds
2010-08-21 20:27 ` Linus Torvalds
2010-08-24 7:43 ` Nick Piggin
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=20100821200528.GA27421@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=samuel.thibault@ens-lyon.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®