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

[PATCH 0/3] update git cvs import documentation

From
Jeff King <peff@peff.net>
Date
Sep 22, 2016, 07:23 UTC
Message-ID
<20160922072350.ivjrfuedodd2rezn@sigill.intra.peff.net>

I dreamed a dream that I would never have to think about git-cvsimport again. And yet. Somebody reported[1] that the link to cvsps in gitcvs-migration is broken. While fixing it, I noticed a few other out-of-date items. I haven't used any of these tools myself in years, but hopefully these changes are minimal no-brainers.

  [1/3]: docs/cvsimport: prefer cvs-fast-export to parsecvs
  [2/3]: docs/cvs-migration: update link to cvsps homepage
  [3/3]: docs/cvs-migration: mention cvsimport caveats
-Peff
[1] https://github.com/git/git-scm.com/issues/851
Next: Jeff King
Message 1 of 9 in “update git cvs import documentation”
  1. 0/3 update git cvs import documentationJeff King, Sep 22, 2016
  2. 1/3 docs/cvsimport: prefer cvs-fast-export to parsecvsJeff King, Sep 22, 2016
  3. 2/3 docs/cvs-migration: update link to cvsps homepageJeff King, Sep 22, 2016
  4. 3/3 docs/cvs-migration: mention cvsimport caveatsJeff King, Sep 22, 2016
  5. Eric S. RaymondSep 22, 2016
  6. Jeff KingSep 23, 2016
  7. Eric S. RaymondSep 28, 2016
  8. Jeff KingSep 28, 2016
  9. Junio C HamanoSep 28, 2016

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.