From: Junio C Hamano <junkio@cox.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: git@vger.kernel.org
Subject: Re: Problem with cg-clone
Date: Sat, 29 Oct 2005 13:19:25 -0700 [thread overview]
Message-ID: <7vslukyt2q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1130616653.5396.56.camel@blade> (Marcel Holtmann's message of "Sat, 29 Oct 2005 22:10:53 +0200")
Marcel Holtmann <marcel@holtmann.org> writes:
>> The attached patch should fix git-local-fetch which I think the
>> above problem is. git-clone -l -s would be much faster if you
>> are doing a local clone, however.
>
> I can confirm that with this patch everything is back to normal.
Thanks. What Linus separately done (funny we did that
two-minutes apart) amounts to the same thing.
prev parent reply other threads:[~2005-10-29 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 17:08 Problem with cg-clone Marcel Holtmann
2005-10-29 19:41 ` Junio C Hamano
2005-10-29 19:57 ` Linus Torvalds
2005-10-29 19:59 ` Junio C Hamano
2005-10-29 20:10 ` Marcel Holtmann
2005-10-29 20:19 ` 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=7vslukyt2q.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=marcel@holtmann.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).