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

git-cvsimport-3 and incremental imports

From
John Keeping <john@keeping.me.uk>
Date
Jan 20, 2013, 20:09 UTC
Message-ID
<20130120200922.GC7498@serenity.lan>

I've now spent some time looking at git-cvsimport-3.py from jc/cvsimport-upgrade and made some progress in making it pass more of the Git test suite (my work in progress is at [1]).

However, I think there is a fundamental problem with the way it handles incremental imports and I'm hoping someone with more git-fast-import experience can point me in the right direction.

Currently, cvsps-3 never writes a "from ..." line in the first commit it outputs for a branch, even when the output is restricted by date (i.e. a continuation of a previously imported branch), which results in failure to update branches since git-fast-import is run without "--force". If I make a simple modification so that it does this, it can end up outputting an empty commit (a duplicate of the current tip commit on the branch).

Given that the start date for the import is currently just read from HEAD there is probably scope for this being worse on other branches if they have more recent commits than the current branch.

I don't think there is any way to solve this without giving cvsps more information, probably the last commit time for all git branches, but perhaps I'm missing a fast-import feature that can help solve this problem.

[1] https://github.com/johnkeeping/git/tree/cvsimport-3
John
Next: Eric S. Raymond
Message 1 of 16 in “git-cvsimport-3 and incremental imports”
  1. John KeepingJan 20, 2013
  2. Eric S. RaymondJan 20, 2013
  3. Jonathan NiederJan 20, 2013
  4. Junio C HamanoJan 21, 2013
  5. Junio C HamanoJan 21, 2013
  6. Jonathan NiederJan 20, 2013
  7. Eric S. RaymondJan 21, 2013
  8. Jonathan NiederJan 21, 2013
  9. Junio C HamanoJan 21, 2013
  10. Junio C HamanoJan 21, 2013
  11. John KeepingJan 21, 2013
  12. Eric S. RaymondJan 21, 2013
  13. John KeepingJan 21, 2013
  14. Eric S. RaymondJan 21, 2013
  15. John KeepingJan 21, 2013
  16. Eric S. RaymondJan 21, 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.