On Fri, Oct 20, 2006 at 10:31:11AM -0400, Jeff King wrote: > On Thu, Oct 19, 2006 at 01:14:09PM -0400, J. Bruce Fields wrote: > > So in this case you can certainly lose the launch codes. But you have > > forever granted everyone a way to determine whether a given guess at the > > launch codes is correct. (Again, assuming some stuff about SHA1). > > In what sense? Yes, you can make a guess if you have stored the SHA1 > that contained the launch codes. But the point is that that particular > SHA1 is no longer part of the repository. 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). > Keeping that SHA1 is no easier than just keeping the launch codes in > the first place. Could be. Anyway, the important difference between the SHA1 references and small integers is that there's no aliasing in the former case. Which is important--I'd rather have a reference to nothing than a reference to the wrong thing.... --b. - 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