From: Junio C Hamano <gitster@pobox.com>
To: Sam Vilain <sam@vilain.net>
Cc: Nicholas Clark <nick@ccl4.org>,
Perl 5 Porters <perl5-porters@perl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: The Reposithon! Take 2 [URL FIX]
Date: Mon, 17 Dec 2007 10:00:57 -0800 [thread overview]
Message-ID: <7vmys98ali.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <476664EB.5030500@vilain.net> (Sam Vilain's message of "Tue, 18 Dec 2007 01:00:43 +1300")
Sam Vilain <sam@vilain.net> writes:
> The error message isn't the best, no.
>
> Junio, any chance of this going in?
Looks innocuous and an obvious improvement to me.
next prev parent reply other threads:[~2007-12-17 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47664617.9010106@vilain.net>
[not found] ` <4766582F.4030207@vilain.net>
[not found] ` <20071217111433.GN23703@plum.flirble.org>
[not found] ` <4766620A.6050704@vilain.net>
[not found] ` <20071217115450.GR23703@plum.flirble.org>
2007-12-17 12:00 ` The Reposithon! Take 2 [URL FIX] Sam Vilain
2007-12-17 18:00 ` Junio C Hamano [this message]
2007-12-17 18:03 ` Nicholas Clark
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=7vmys98ali.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nick@ccl4.org \
--cc=perl5-porters@perl.org \
--cc=sam@vilain.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).