| 1 |
On Tue, Apr 14, 2015 at 4:33 PM, Alexander Berntsen <bernalex@g.o> wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA256 |
| 4 |
> |
| 5 |
> On 11/04/15 17:48, Zac Medico wrote: |
| 6 |
>> Apparently this is what git send-email does when you send a patch |
| 7 |
>> after using the git commit --author option to set a different |
| 8 |
>> other. I'm not sure if this is configurable. |
| 9 |
> Oh, of course. I forgot about that. It's quite useless, because if you |
| 10 |
> am one of those patches, it will just set the author to the committer. |
| 11 |
> |
| 12 |
|
| 13 |
git-format-patch seems to indicate that git-am will pick up the From: |
| 14 |
line int the body and this should "just work". |
| 15 |
|
| 16 |
--from, --from=<ident> |
| 17 |
Use ident in the From: header of each commit email. If the |
| 18 |
author ident of the commit is not textually identical to the |
| 19 |
provided ident, place a From: header in the body of the message |
| 20 |
with the original author. If no ident is given, use the |
| 21 |
committer ident. |
| 22 |
|
| 23 |
Note that this option is only useful if you are actually |
| 24 |
sending the emails and want to identify yourself as the sender, |
| 25 |
but retain the original author (and git am will correctly pick |
| 26 |
up the in-body header). Note also that git send-email already |
| 27 |
handles this transformation for you, and this option should not |
| 28 |
be used if you are feeding the result to git send-email. |
Archives