From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Joe Perches <joe@perches.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
git <git@vger.kernel.org>
Subject: Re: [PATCH] include/asm-arm/: Spelling fixes
Date: Mon, 17 Dec 2007 13:27:20 -0800 [thread overview]
Message-ID: <7vy7bt57wn.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071217205134.GB2105@coredump.intra.peff.net> (Jeff King's message of "Mon, 17 Dec 2007 15:51:34 -0500")
Jeff King <peff@peff.net> writes:
> Ah. The problem is that git-send-email unconditionally adds a
> message-id. Usually git-format-patch doesn't add one, but for obvious
> reasons, it must when doing --thread. Here is a fix.
> diff --git a/git-send-email.perl b/git-send-email.perl
> index 1d6f466..083466a 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -580,7 +580,7 @@ sub send_message
> $ccline = "\nCc: $cc";
> }
> my $sanitized_sender = sanitize_address($sender);
> - make_message_id();
> + make_message_id() unless defined($message_id);
Isn't this called inside a loop? If the outgoing message does not
originally have "Message-Id:", does the loop correctly reinitialize
$message_id to undef, or does this change make everybody reuse the same
$message_id over and over again?
I have a feeling that --thread to format-patch is a misfeature. Why is
it needed if you are feeding the output to send-email?
I wonder if stripping existing "Message-Id:" away just like we strip
away "Date:" from @xh would be a much saner fix.
next prev parent reply other threads:[~2007-12-17 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5703e57f925f31fc0eb38873bd7f10fc44f99cb4.1197918889.git.joe@perches.com>
[not found] ` <20071217195658.GB13515@fieldses.org>
[not found] ` <1197921847.27386.16.camel@localhost>
2007-12-17 20:12 ` [PATCH] include/asm-arm/: Spelling fixes J. Bruce Fields
2007-12-17 20:22 ` Joe Perches
2007-12-17 20:51 ` Jeff King
2007-12-17 21:27 ` Junio C Hamano [this message]
2007-12-17 23:05 ` Jeff King
2007-12-17 23:12 ` Jeff King
2007-12-17 23:28 ` Junio C Hamano
2008-01-08 11:15 ` Josh Triplett
2008-01-08 11:16 ` Josh Triplett
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=7vy7bt57wn.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=joe@perches.com \
--cc=peff@peff.net \
/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).