On Tue, 29 Aug 2006, Johannes Schindelin wrote: > > > Nope. If it has the same SHA1, it means that when we receive the object > > from the other end, we will _not_ overwrite the object we already have. > > The only notable exception I can think of: "git fetch -k". If you then try > to retrieve the bogus object, it will return the one of whichever pack was > returned first be readdir(). (If I read the source correctly.) Good point. I didn't even think of "-k", since I mentally put that in the "initial clone usage only" category, but yeah, if people use it for incremental updates too, that could indeed cause ambiguity in which object to use when the other end does something bad. Linus - 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