Theodore Tso <tytso@xxxxxxx> writes: >> The arguments to make are "Junio is worrying too much; depending on the >> other repository's ref is no worse than depending on the objects the other >> repository uses, and here is a proof that it is not just 'not a big deal' >> but 'no problem at all'", "I've polled the userbase and there is no >> existing configuration that will be broken by this change", and "I have >> this configuration that will be broken by above change, don't do it". > > So the only configuration I can think of that would be broken by this > is where $D/refs exists, but is insane. (i.e., such that git fsck for > $D would result in errors). That seems pretty unlikely... I was more worried about "once $D/ started its life as an actively used and maintained repository, but it itself has been abandoned and its refs are not maintained anymore; only $D/objects are still in use", but even in that case, it won't be "$D/refs exists but insane" case, so we should be Ok. -- 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
