Andi Kleen <a...@firstfloor.org>:
> But I don't really understand the problem. Just run git log
> and generate your own list of numbers. Should be straight forward
> to script.
I can tell you from experience with lots of conversions that this, and
the other proposals in the thread, are what our British friends call
"too clever by half". One defect is that they assume SHA hashes
of commits will be valid forever. But this assumnption could easily break
if either (a) the repository requires surgery in he future, or (b) GCC ever
changes version-control systems again.
What I usually do with old commit references in comments is map them
to what I call an "action stamp" - a user ID followed by an RFC3339
date. While this is theoretically not quite adequate, in practice
collisions are rare to nonexistent.
Action stamps have the major advantages that they are self-describing and
should remain valid and scrutable in the future under any reasonable
transformation of the repository.
Jason should make the policy decision, but this is what I recommend.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
