All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, 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: Tue, 08 Jan 2008 03:15:43 -0800	[thread overview]
Message-ID: <47835B5F.3030204@freedesktop.org> (raw)
In-Reply-To: <7vy7bt57wn.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> 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 added that option; see (d1566f7883f727f38bf442af3fdb69d36e6fcea2,
cc35de8470541e389b7d2bdda4c901574720fa81, and
da56645dd7c1175fc2ed1628ac35fdd35e705641).  I use git-imap-send, not
git-send-email, and I wanted to thread my patches.

- Josh Triplett

  parent reply	other threads:[~2008-01-08 11:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 19:30 [PATCH] arch/ia64/: Spelling fixes Joe Perches
2007-12-17 19:30 ` [PATCH] arch/arm/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/asm-arm/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/blackfin/: " Joe Perches
2007-12-17 19:49   ` [Uclinux-dist-devel] " Mike Frysinger
2007-12-17 19:30 ` [PATCH] arch/h8300/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/ia64/: " Joe Perches
2007-12-18  7:49   ` Jes Sorensen
2007-12-18  7:49     ` Jes Sorensen
2007-12-17 19:30 ` [PATCH] include/asm-ia64/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/m32r/: " Joe Perches
2007-12-17 19:30 ` [PATCH] arch/mips/: " Joe Perches
2007-12-17 19:56 ` [PATCH] include/asm-arm/: " J. Bruce Fields
     [not found]   ` <1197921847.27386.16.camel@localhost>
2007-12-17 20:12     ` 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
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 [this message]
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=47835B5F.3030204@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.