git/list[1] front-page[2] threads[3] people[4] search[5] about
 

cvs revision number -> git commit name?

From
HFHallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date
Jan 26, 2010, 21:53 UTC
Message-ID
<hbf.20100126bda0@bombur.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
Next: Aaron Crane
Message 1 of 7 in “cvs revision number -> git commit name?”
  1. Hallvard B FurusethJan 26, 2010
  2. Aaron CraneJan 26, 2010
  3. Johan HerlandJan 26, 2010
  4. Junio C HamanoJan 27, 2010
  5. Johan HerlandJan 27, 2010
  6. Hallvard B FurusethJan 27, 2010
  7. Johan HerlandJan 27, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.