From: "Ian Dees" <undees@gmail.com>
To: git@vger.kernel.org
Cc: peff@peff.net, jnareb@gmail.com
Subject: Re: Completion message for git-clone?
Date: Fri, 8 Feb 2008 08:23:23 -0800 [thread overview]
Message-ID: <ad4f9af90802080823g64b44d27lb870e849e106743b@mail.gmail.com> (raw)
In-Reply-To: <m3ejbn4vis.fsf@localhost.localdomain>
Hi, all.
Thanks, Jeff and Jakub, for the clarifications.
Jakub writes:
> Nevertheless git-clone waits to be rewritten in C anyway, so
> there is no much initiative to improve shell version
I agree with you. If it's about to be replaced, there's not much
point in making a wording change to the shell script.
> Perhaps git should check if there is anything to clone _before_
> git-init, or do not remove empty directory after failing to fetch.
I'm not sure that's necessary, as long as that new message is there in
1.5.4. I'll hang tight for my distro to pick it up.
--Ian
prev parent reply other threads:[~2008-02-08 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 3:09 Completion message for git-clone? Ian Dees
2008-02-08 8:29 ` Jeff King
2008-02-08 10:01 ` Jakub Narebski
2008-02-08 16:23 ` Ian Dees [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=ad4f9af90802080823g64b44d27lb870e849e106743b@mail.gmail.com \
--to=undees@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).