From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Patch submission process (was: [PATCH] Add "Line In" input jack constants)
Date: Thu, 6 Oct 2011 11:00:37 +0100 [thread overview]
Message-ID: <20111006100037.GA14518@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E8D4EBE.6030703@canonical.com>
On Thu, Oct 06, 2011 at 08:46:22AM +0200, David Henningsson wrote:
> On 10/05/2011 05:07 PM, Mark Brown wrote:
> >but please follow the patch submission process in SubmittingPatches - in
> >particular, don't send your patch as an attachment.
> I find this hard to fulfil at times, in particular when I want to
> add something to the email that I don't want to be a part of the
> commit message. Is this possible with git send-email, and without
> sending the patch as an attachment?
The relevant section of SubmittingPatches is:
| - A marker line containing simply "---".
|
| - Any additional comments not suitable for the changelog.
|
| - The actual patch (diff output).
You can edit the patch after running format-patch, or use --annotate
with send-mail.
next prev parent reply other threads:[~2011-10-06 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 14:01 [PATCH] Add "Line In" input jack constants David Henningsson
2011-10-05 14:08 ` Takashi Iwai
2011-10-05 15:07 ` Mark Brown
2011-10-06 6:23 ` Takashi Iwai
2011-10-06 7:29 ` David Henningsson
2011-10-06 6:46 ` Patch submission process (was: [PATCH] Add "Line In" input jack constants) David Henningsson
2011-10-06 8:55 ` Patch submission process Clemens Ladisch
2011-10-06 10:00 ` Mark Brown [this message]
2011-10-05 15:55 ` [PATCH] Add "Line In" input jack constants Takashi Iwai
2011-10-06 3:36 ` Dmitry Torokhov
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=20111006100037.GA14518@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=tiwai@suse.de \
/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.