• Post Reply Bookmark Topic Watch Topic
  • New Topic

any alternative to cvs2svn?  RSS feed

Niranjan Deshpande
Ranch Hand
Posts: 1277
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I migrated my projects from cvs, to svn. and used the cvs2svn tool for that. Other than the source dir and the destinton dir tht i used in the command line, following options were used

--fs-type=fsfs, --fallback-encoding=UTF8
The migration happen properly. But we found that the svn commit history for the source files is not the same as it was in cvs.

fr e.g fr a source file cvs shows 13 commit entries, but upon seeing in svn, we get to see lesser number of commit histories.
commit entries are missing.

This is what the cvs2svn mialing list told me

There is no such problem known.

Please read in the cvs2svn features [1] about some kinds of redundant
commits that cvs2svn leaves out of the conversion because they are

If you are still convinced that there is a problem, please submit a
proper bug report including a reproducible test case. The FAQ [2]
contains instructions for doing so. In particular, describe how you
determined the number of commits in CVS and the number in SVN.

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

[2] [URL=http://cvs2svn.tigris.org/faq.html

would like to know this:

1. How does the tool decide if some commit entry is meaningless? Does it actually see what was changed to decide if it's really necessary to retain the history or not?

I saw this in the cvs2svn features:
Unfortunately, CVS doesn't record complete information about your project's history. For example, CVS doesn't record what file modifications took place together in the same CVS commit. Therefore, cvs2svn attempts to infer from CVS's incomplete information what really happened in the history of your repository. So the second goal of cvs2svn is to reconstruct as much of your CVS repository's history as possible.

Is this some disclaimer 'The complete history for the source file will not be seen when its migrated from cvs2svn'? My understanding on the above: If there are, say 10 commit entries for a source file, then the tool actually analyzes and decides what all entries to keep in the commit histroy when it reocords the history with svn. Do we have a criteria documented somewhere, which the tool uses while migrating the history? I can have a a look at it, and accordingly decide if we really lost some commit entries, or the tol just infered that the entries were meaningles and so did not migrate them to svn.

Also are there any alternatives other than cvs2svn?

[ August 04, 2008: Message edited by: Niranjan Deshpande ]
[ August 04, 2008: Message edited by: Niranjan Deshpande ]
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!