From: Junio C Hamano <junkio@cox.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jody McIntyre <scjody@modernduck.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux1394-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ben Collins <bcollins@ubuntu.com>
Subject: Re: [git pull] ieee1394 tree for 2.6.18
Date: Wed, 21 Jun 2006 05:01:32 -0700 [thread overview]
Message-ID: <7v7j3azpib.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <44991622.2000109@s5r6.in-berlin.de> (Stefan Richter's message of "Wed, 21 Jun 2006 11:49:22 +0200")
Stefan Richter <stefanr@s5r6.in-berlin.de> writes:
> A related question: If a patch written by author A is forwarded via
> e-mail by person B to git tree maintainer C, and C imports the mail with
> git-am or git-applymbox --- will git catch the _last_ "From: " line
> (hopefully listing the address of A) or the first "From: " line (which
> contains the forwarding address of B) as author of the patch?
>
> Similarly, will it care for the last or first "Subject: " line? (The
> first line being the actual mail header, the last being a line in the
> mail body or a line in a plain-text encoded attachment, that is.)
The main question was answered by Ben, so this may be a bit
offtopic, but I'll answer git questions anyway.
The author-name-email, subject, and author-date are taken from
the RFC2822 headers of the e-mail the committer feeds git-am,
but you can override them by having "From: ", "Subject: ", and
"Date: " as the first lines of the message body, like this:
From: "For W. Arder" <forwarder@example.com>
Date: Wed, 21 Jun 2006 11:49:22 +0200
Subject: forwarding patch (was Re: ieee1394)
Message-ID: ...
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: Mon Jun 12 18:16:25 2006 -0400
Subject: eth1394: replace __constant_htons by htons
...and __constant_ntohs, __constant_ntohl, __constant_cpu_to_be32 too
where possible. Htons and friends are resolved to constants in these
places anyway. Also fix an endianess glitch in a log message, spotted
by Alexey Dobriyan.
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Note that the latter three header-looking lines are not RFC2822
headers but part of your (eh, Mr Arder's) message body.
prev parent reply other threads:[~2006-06-21 12:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 12:03 Stefan Richter
2006-06-20 2:06 ` Linus Torvalds
2006-06-20 2:55 ` Al Viro
2006-06-20 3:14 ` Linus Torvalds
2006-06-20 4:22 ` Al Viro
2006-06-20 4:31 ` Al Viro
2006-06-20 4:35 ` Roland Dreier
2006-06-20 17:53 ` Russell King
2006-06-20 19:29 ` Stefan Richter
2006-06-20 19:34 ` Russell King
2006-06-20 20:02 ` Dave Neuer
2006-06-20 20:22 ` Al Viro
2006-06-20 21:15 ` Dave Neuer
2006-06-20 21:40 ` Linus Torvalds
2006-06-20 20:57 ` Stefan Richter
2006-06-20 21:03 ` Stefan Richter
2006-06-20 21:15 ` Al Viro
2006-06-21 17:08 ` Ryan Anderson
2006-06-20 21:25 ` Linus Torvalds
2006-06-20 10:38 ` Stefan Richter
2006-06-21 3:07 ` Linus Torvalds
2006-06-21 6:32 ` Ben Collins
2006-06-21 9:49 ` Stefan Richter
2006-06-21 10:27 ` Ben Collins
2006-06-21 12:01 ` Junio C Hamano [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=7v7j3azpib.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=akpm@osdl.org \
--cc=bcollins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=scjody@modernduck.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@osdl.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®