On Fri, Oct 20, 2006 at 11:33:23AM -0400, J. Bruce Fields wrote: > Well, I thought the discussion was about what meaning references have > after branches were modified or removed. In which case the interesting > situation is one where an object is gone but someone somewhere still > holds a reference (because the SHA1 was mentioned in a bug report or an > email or whatever). Git tries very hard to make sure you don't have a reference to something that doesn't exist. But yes, you could have a reference to the SHA1 in another, non-git source, and try to guess the data from it. However, there's a bit of a two-step procedure, since the SHA1 will likely be of the commit. You have to guess the commit author, date, message, and the contents of the rest of the tree to make a correct guess. In practice I think most "launch code" scenarios are less about guessable confidentiality, and more about ceasing to publish things you shouldn't be (like copyright or patent encumbered code). -Peff - 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