On Wed, 20 Jul 2011, david@xxxxxxx wrote: > On Wed, 20 Jul 2011, George Spelvin wrote: > > > > The alternative of having to sometimes use the generation number, > > > sometimes use the possibly broken commit date, makes for much more > > > complicated code that has to be maintained forever. Having a solution > > > that starts working only after a certain point in history doesn't look > > > eleguant to me at all. It is not like having different pack formats > > > where back and forth conversions can be made for the _entire_ history. > > > > It seemed like a pretty strong argument to me, too. > > except that you then have different caches on different systems. So what? > If the generation number is part of the repository then it's going to > be the same for everyone. The actual generation number will be, and has to be, the same for everyone with the same repository content, regardless of the cache used. It is a well defined number with no room to interpretation. > in either case, you still have the different heristics depending on what > version of git someone is running Indeed. Nicolas -- 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