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

cvsexportcommit/cvsimport workflow

From
ALAlexander Litvinov <lan@ac-sw.com>
Date
Nov 21, 2005, 14:43 UTC
Message-ID
<200511212043.57434.lan@ac-sw.com>
Hello,
Can ypu please explain how to use cvsimport with cvsexportcommit scripts ? 
I have tried these steps:
1. Make git repo from cvs repo using cvsimport command - everything works 
great.
2. Start traking cvs changes by incremental running cvsimport - It works.
3. Change files in git repo (master branch) - works :-)
4. Export git commits to cvs: 
      first question: What should be exported and in what order ? Lets skip 
this part - it is the smallest problem.
      Two test commits were exported to cvs without any problmes.
5. Importing cvs again - I have found my exported commits became separate 
commits in git repo in origin branch (solved by git-pull . origin). But thay 
were merged idealy.
6. Changing files again in git.
7. Export git commits to cvs: What should be exported question become harder 
and harder. Possible I should use some tag and run:
git-rev-list MY-TAG..master | xargs -n 1 git-cvsexportcommit -vX -cX (by the 
way, why just -v -c does not work ? I must add something to make options 
work)

This cycle is a bit of mess. I can write some scripts but I have no idea how this is supposed to work !

The biggest problem - conflict. I should resove them twice, during merging origin branch to master and when exporting these changes to cvs. By the way, I still can't export merge commit :-)

Thanks for help. Alexander Litvinov.

Next: Martin Langhoff
Message 1 of 2 in “cvsexportcommit/cvsimport workflow”
  1. Alexander LitvinovNov 21, 2005
  2. Martin LanghoffDec 5, 2005

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.