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

Re: [PATCH 0/3] fixup remaining cvsimport tests

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jan 24, 2013, 03:15 UTC
Message-ID
<5100A766.8050902@alum.mit.edu>
In-Reply-To
<20130123110312.GK7498@serenity.lan>
On 01/23/2013 12:03 PM, John Keeping wrote:
Show 12 quoted lines
> On Wed, Jan 23, 2013 at 10:54:36AM +0100, Michael Haggerty wrote:
>> On 01/20/2013 09:17 PM, Chris Rorvick wrote:
>>> I have never used cvs2git, but I suspect Eric's efforts in making it a
>>> potential backend for cvsimport are a better use of time.
> 
> Is it possible to perform an incremental import with cvs2git?  This
> seems to be the one use case where the old cvsimport script (with cvsps
> 2.x) still performs the best.
> 
> I suppose that just re-running the full import will do the right thing
> since the commits in Git should be identical, but would it be possible
> to do better given the right information about a previous run?

No, cvs2git does not support incremental imports. One user has reported that he *usually* gets identical commits for the overlapping history when he re-runs a full import, and last I heard he was using this as a kind of incremental import. We make an effort to make imports reproducible, at least when using a single version of cvs2git (for example, we process things in deterministic order rather than the order they happen come out of a file directory or Python hashmap). But the cycle-breaking heuristics in particular can give different results if history is added, not to mention the fact that CVS allows the user to make changes with retroactive and non-timestamped effects (e.g., adding or removing files from an existing branch/tag, changing a file's default branch from vendor to HEAD, changing the log messages of old revisions, obsoleting revisions). And if your repository is large, a full import can take a while.

It would be possible to enhance cvs2git to handle incremental imports (well, at least if you rule out a few CVS commands that change deep history). But I don't believe anybody is working on this.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: John Keeping
Message 16 of 16 in “fixup remaining cvsimport tests”
  1. 0/3 fixup remaining cvsimport testsChris Rorvick, Jan 11, 2013
  2. 1/3 t/lib-cvs.sh: allow cvsps version 3.x.Chris Rorvick, Jan 11, 2013
  3. 2/3 t9600: fixup for new cvsimportChris Rorvick, Jan 11, 2013
  4. 3/3 t9604: fixup for new cvsimportChris Rorvick, Jan 11, 2013
  5. John KeepingJan 20, 2013
  6. Chris RorvickJan 20, 2013
  7. John KeepingJan 20, 2013
  8. Junio C HamanoJan 20, 2013
  9. John KeepingJan 20, 2013
  10. Chris RorvickJan 20, 2013
  11. Chris RorvickJan 20, 2013
  12. Chris RorvickJan 21, 2013
  13. Eric S. RaymondJan 21, 2013
  14. Michael HaggertyJan 23, 2013
  15. John KeepingJan 23, 2013
  16. Michael HaggertyJan 24, 2013

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.