Because I do a lot of work on repository conversion tools, I've had to learn a lot of detail about ontological mismatches between version-control systems - especially places where you lose metadata moving between them. In general, git metadata can carry forward almost all the metadata in a Subversion repository. Among the handful of minor exceptions (empty directories, flow structure, certain kinds of mergeinfos) there is one that stands out because it seems to be an implementation detail rather than a consequence of fundamentally different design decisions. I refer to the one-second precision of git timestamps. Subversion stores its commit and property-change timestamps to microsecond precision; conversion tools have to throw the subsecond part of this information away. Has going to timestamps with the full precision of the system clock been considered and rejected, or am I the first to bring this up? If I were to write refactoring patches that treated "timestamp" as an ADT, with a view towards hiding the difference between int and float timestamps and eventually experimenting with float ones, would they be accepted? -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> Every Communist must grasp the truth, 'Political power grows out of the barrel of a gun.' -- Mao Tse-tung, 1938, inadvertently endorsing the Second Amendment. -- 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