Re: 'git clone' doesn't use alternates automatically?
- From
- James Pickens <jepicken@gmail.com>
- Date
- Jan 31, 2009, 21:43 UTC
- Message-ID
- <885649360901311343r2a9bd1b5l5f8226218000dbe8@mail.gmail.com>
- In-Reply-To
- <m3tz7fw5ek.fsf@localhost.localdomain>
On Sat, Jan 31, 2009 at 2:08 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 8 quoted lines
> James Pickens <jepicken@gmail.com> writes: > >> So, is there any reason 'git clone' shouldn't automatically use >> the alternates that it copied into the new repository? I might >> look into writing a patch if nobody objects. > > Alternates are fragile with respect to garbage collecting in the > repository you borrow objects from.
I think that's irrelevant in this case. The scenario is that I clone repo A, which is borrowing objects from repo B. So repo A was already assuming that it's safe to borrow from B.
The current behavior is that the clone of A also borrows from B automatically. What I am asking is whether 'git clone' should take advantage of that to avoid copying redundant objects from A into the clone. They will get deleted the first time I run 'git gc' in the clone anyways.
James