From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Patches for 34K APRP
Date: Thu, 17 Apr 2008 13:10:01 +0100 [thread overview]
Message-ID: <20080417121001.GA30873@linux-mips.org> (raw)
In-Reply-To: <48060258.8050904@mips.com>
On Wed, Apr 16, 2008 at 03:42:48PM +0200, Kevin D. Kissell wrote:
> Sigh. Some mailers (including Thunderbird for Windows)
> seem to be unable to handle the attachment of the patch
> files by Thunderbird. So I attach them as a .tgz, which
> even Outlook should be able to deal with correctly.
With the kernel maintainers head hidden for a moment - the attachments
certainly were ok, I was able to feed them to patch and had no problems
applying them.
With the kernel maintainers hat firmly back on the head:
o git will use the Subject: line followed by the body followed by the
attachment's leading comment as the commit message for the patch.
Anything after a "---" tearoff line such a signature will be dropped.
For the submitter that means to ensure only things that are meant to
go into the log should be before the tearoff line.
o As the result of this method git will only be able to handle a single
patch per email. But that's not a problem anyway. Patches are meant
to be easily discussable by email and that's best done with a single
patch per mail.
I'm going to send comments on the actual patch by separate email.
Ralf
next prev parent reply other threads:[~2008-04-17 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 13:32 Patches for 34K APRP Kevin D. Kissell
2008-04-16 13:42 ` Kevin D. Kissell
2008-04-17 12:10 ` Ralf Baechle [this message]
2008-04-17 12:29 ` Ralf Baechle
2008-04-17 12:43 ` Ralf Baechle
2008-04-17 13:38 ` Kevin D. Kissell
2008-04-18 9:52 ` Ralf Baechle
2008-04-17 13:26 ` Ralf Baechle
2008-04-17 13:43 ` Kevin D. Kissell
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=20080417121001.GA30873@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.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.