cvs revision number -> git commit name?

[Hallvard B Furuseth <h.b.furuseth@usit.uio.no>]

When moving from CVS to Git, what's a good way to help Git users
find an old commit given the original CVS revision number?  Are
there tools available to help?

There are plenty of still-useful references to CVS revisions
floating around - in bug reports, mailing list archives, commit
messages referring to other commits.  Some loose thoughts:

One could commit a table with a (file,revision)->commit mapping,
I suppose something can generate it when importing from cvs?

Many but far from all old file contain the CVS ID, named $OpenLDAP$.
Can Git grep all versions of a file for '\$OpenLDAP:.* 1.23 '?

Could maybe add a line like this to many of the log messages:
    "<cvs: version 1.23>"
for single-file commits, or
    "<cvs: here/foo.c 1.23, there/bar.c 1.45>"
for multi-file comments with few enough files that such an
annotation fits on one line.  That'll make log messages like "fix
rev 1.23" easier to read without need for a tool to find what the
message is talking about, but does clutter up the log a lot.

Some stats:
    1600 files = 23M text, 770k lines, in 100 directories.
   Maybe 20000 Git commits, 50M ldap.git/.git/ directory.

-- 
Hallvard