From: Junio C Hamano <gitster@pobox.com>
To: David Aguilar <davvid@gmail.com>
Cc: Sebastian Pipping <sebastian@pipping.org>,
git@vger.kernel.org, spearce@spearce.org
Subject: Re: [PATCH 3/3] mergetool-lib: add diffuse as merge and diff tool
Date: Thu, 02 Apr 2009 11:06:07 -0700 [thread overview]
Message-ID: <7vhc17exrk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20090402104252.GA29223@gmail.com
David Aguilar <davvid@gmail.com> writes:
> git-send-email (probably gmail, too) won't let me send
> one patch in a series with a different "From:" header,
> so maybe you should resend this patch so that you can get the
> proper authorship recognition? I've attached the original
> patch file I sent in case you want to just grab it and
> send-email it back out for the purposes of getting the right
> authorship in there (actually, Junio, please advise...,
> I'm not exactly sure what you'd prefer)
The way you marked your 3/3 with a From: line in the body of the message
is the preferred way to say "David forwards a patch from Sebastian", and
our patch application tool knows about it.
If you wanted to preserve the original author date, you could have also
added a Date: line in-body ("David forwards a patch from Sebastian, who
created it at this date in this timezone"). You can find an earlier
example in:
http://article.gmane.org/gmane.comp.version-control.git/115289
next prev parent reply other threads:[~2009-04-02 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 10:30 [PATCH 1/3] mergetool-lib: specialize kdiff3 options when in diff mode David Aguilar
2009-04-02 10:30 ` [PATCH 2/3] mergetool-lib: specialize xxdiff " David Aguilar
2009-04-02 10:30 ` [PATCH 3/3] mergetool-lib: add diffuse as merge and diff tool David Aguilar
2009-04-02 10:42 ` David Aguilar
2009-04-02 18:06 ` Junio C Hamano [this message]
2009-04-02 21:20 ` [PATCH 2/3] mergetool-lib: specialize xxdiff options when in diff mode Markus Heidelberg
2009-04-03 1:56 ` David Aguilar
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=7vhc17exrk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=sebastian@pipping.org \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).