On Sat, Jan 31, 2009 at 2:08 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > James Pickens <jepicken@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
