From: Junio C Hamano <gitster@pobox.com>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Brown paper bag fix to previous send-email change
Date: Tue, 11 Dec 2007 00:06:06 -0800 [thread overview]
Message-ID: <7vlk81fyfl.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071211074427.GA12959@glandium.org> (Mike Hommey's message of "Tue, 11 Dec 2007 08:44:28 +0100")
Mike Hommey <mh@glandium.org> writes:
>> No, I happened to have noticed the same and have an almost identical fix
>> (I said "defined $initial_reply_to") already queued in my tree.
>
> Testing "defined $initial_reply_to" might not be enough, because $initial_reply_to
> can be defined and empty.
Ah, I see what you mean. Thanks.
prev parent reply other threads:[~2007-12-11 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 6:55 [PATCH] Brown paper bag fix to previous send-email change Mike Hommey
2007-12-11 7:04 ` Junio C Hamano
2007-12-11 7:44 ` Mike Hommey
2007-12-11 8:02 ` Junio C Hamano
2007-12-11 8:06 ` Junio C Hamano [this message]
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=7vlk81fyfl.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).