Re: 'git clone' doesn't use alternates automatically?

From: James Pickens <jepicken@gmail.com>
Date: Feb 1, 2009, 01:32 UTC
Message-ID: <885649360901311732t6e4f8651p6c3955f018b9a36c@mail.gmail.com>
In-Reply-To: <7vtz7f2cy6.fsf@gitster.siamese.dyndns.org>

On Sat, Jan 31, 2009, Junio C Hamano <gitster@pobox.com> wrote:

> When you say "git clone" without -s, you are saying "I do not want to use
> the repository I am cloning from as my alternate, because I do not know if
> will stay stable.  I do not trust it."

Yes, I'm aware of the caveats of -s. I was talking about what happens when I *don't* use -s.

> Now, if you are cloning from a local filesystem, by default we will copy
> the objects/info/alternates from the source repository to the new one.  It

Crap, I didn't realize the alternates were only copied when you clone from the local filesystem. I wanted to use this when cloning over ssh from site A to site B, to automatically add a mirror at site B as an alternate. Sounds like I have no choice but to use --reference for that.

> I suspect you are trying to improve the other extreme end: trusting all
> the other repositories involved in the cloning process a lot more than the
> code currently does.

What I was suggesting did not involve trusting anything any more than the current code does. It just meant taking immediate advantage of the trust that was already there.

Thanks for your input, James