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, 07:47 UTC
Message-ID
<48ABCBFD.7070503@alum.mit.edu>
In-Reply-To
<48ABC943.20508@bluelane.com>
Pete/Piet Delaney wrote:
Show 7 quoted lines
> Michael Haggerty wrote:
>> 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].
> [...]
> 
>   How does your proposed cvs2git facility deal with importing on top
> of branches that have been modified?

cvs2svn/cvs2git does not support this (called "incremental imports"). It is quite hard to implement robustly. In fact, I claim that no tool handles incremental imports robustly, despite the fact that some claim to do so :-)

Michael
Previous: Pete/Piet DelaneyNext: Matthias Urlichs
Message 4 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.