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

Re: git-cvsimport - losing changes in subsequent pulls of a CVS branch that I thought I wasn't modifying in the GIT repo.

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Aug 20, 2008, 06:24 UTC
Message-ID
<48ABB899.4090608@alum.mit.edu>
In-Reply-To
<48AA6F8E.70807@bluelane.com>
Pete/Piet Delaney wrote:
> I'm running into a problem with git-cvsimport.  [...]
> 
> I'll take another stab at it tomarrow. Any thoughts or
> recommendations appreciated.
If this is a one-time conversion (i.e., you don't need to actively track
a live CVS repository), then I suggest that you try cvs2svn/cvs2git [1].
 It can migrate to git via a git-fast-import output stream [2].  All
cvsps-based tools necessarily have problems because cvsps (a) doesn't
output enough information for a reliable conversion and (b) gets
confused by certain patterns that commonly occur in CVS repository
histories.  cvs2svn can handle every CVS repository that we have seen
and is also highly configurable [3].
Michael

[1] http://cvs2svn.tigris.org/ [2] http://cvs2svn.tigris.org/cvs2git.html [3] http://cvs2svn.tigris.org/features.html

Previous: Pete/Piet DelaneyNext: Pete/Piet Delaney
Message 2 of 5 in “git-cvsimport - losing changes in subsequent pulls of a CVS branch that I thought I wasn't modifying in the GIT repo.”
  1. Pete/Piet DelaneyAug 19, 2008
  2. Michael HaggertyAug 20, 2008
  3. Pete/Piet DelaneyAug 20, 2008
  4. Michael HaggertyAug 20, 2008
  5. Matthias UrlichsAug 20, 2008

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.