From: Paolo Bonzini <bonzini@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/2] git-am: add --message-id/--no-message-id options
Date: Tue, 25 Nov 2014 20:16:18 +0100 [thread overview]
Message-ID: <5474D582.9060604@gnu.org> (raw)
In-Reply-To: <xmqqwq6jruyd.fsf@gitster.dls.corp.google.com>
On 25/11/2014 19:33, Junio C Hamano wrote:
>> > If both --message-id and -s are specified, the Signed-off-by goes
>> > last. This is coming out more or less naturally out of the git-am
>> > implementation, but is also tested in t4150-am.sh.
> Nice. So if you apply a message whose last sign-off is yourself
> with both of these options, what would we see?
>
> 1. S-o-b: you and then M-id: and then another S-o-b: you?
> 2. M-id: and then S-o-b: you?
> 3. S-o-b: you and then M-id:?
>
> I do not offhand know which one of the above possibilities to favor
> more over others myself. Just asking to find out more about the
> thinking behind the design.
You currently get (1), which is arguably the most precise but definitely
the ugliest.
In this case (posting as maintainer), I would probably not use "git am
--message-id"; instead I would use an alias to add the Message-Id (with
git interpret-trailers!) after posting to the mailing list, resulting in
either (2) or (3).
I think (but I am not sure) that git-am could use a hook to rewrite (1)
into (2) or (3).
Paolo
next prev parent reply other threads:[~2014-11-25 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 14:00 [PATCH 0/2] git-am: add --message-id/--no-message-id options Paolo Bonzini
2014-11-25 14:00 ` [PATCH 1/2] git-mailinfo: add --message-id Paolo Bonzini
2014-11-25 14:00 ` [PATCH 2/2] git-am: add --message-id/--no-message-id Paolo Bonzini
2014-11-25 23:34 ` Junio C Hamano
2014-11-26 7:06 ` Paolo Bonzini
2014-11-25 16:27 ` [PATCH 0/2] git-am: add --message-id/--no-message-id options Christian Couder
2014-11-25 17:01 ` Paolo Bonzini
2014-11-25 21:21 ` Christian Couder
2014-11-26 9:07 ` Paolo Bonzini
2014-11-27 0:23 ` Christian Couder
2014-11-25 18:33 ` Junio C Hamano
2014-11-25 19:16 ` Paolo Bonzini [this message]
2014-11-25 20:05 ` Junio C Hamano
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=5474D582.9060604@gnu.org \
--to=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pbonzini@redhat.com \
/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).