Diff for "InstructionsforHgcvsimport"

Differences between revisions 3 and 4

make a copy of your cvs repository (not a checkout, but a copy)

cp cvsroot tmpdir

checkout the copy, cd into the checkout

TZ=UTC cvsps -u -A -q > ../cvsps.dump
cd ..
TZ=UTC hg-cvs-import cvsroot cvsmodule hg-rep mapfile < cvsps.dump

module is the cvs module (ie cvs checkout module)

mapfile should be empty the first time the import is run. It records a mapping of hg csets to cvsps commits.

As your cvs repo updates, you can run cvsps again and then run the importer again to update. As long as you use the same mapfile, it will pick up where it left off last time.

CategoryConversion CategoryHowTo

-  ⇤ ← Revision 3 as of 2008-03-30 00:58:30 → 
  Size: 644
  Editor: abuehl
  Comment: +cat
+   ← Revision 4 as of 2008-11-22 02:43:02 → ⇥
  Size: 644
  Editor: IgorTamara
  Comment: wiki sintax
-Deletions are marked like this.
+Additions are marked like this.
 Line 2:
+{{{
 Line 4:
+}}}
 Line 6:
+{{{
 Line 8:
-Line 10:
+Line 9:
-Line 12:
+Line 10:
+}}}
-Line 15:
+Line 13:
-mapfile should be empty the first time the import is run.  It records a
+mapfile should be empty the first time the import is run.  It records a mapping of hg csets to cvsps commits.
-Line 17:
+Line 15:
-mapping of hg csets to cvsps commits

As your cvs repo updates, you can run cvsps again and then run the

importer again to update.  As long as you use the same mapfile, it will

pick up where it left off last time.
+As your cvs repo updates, you can run cvsps again and then run the importer again to update.  As long as you use the same mapfile, it will pick up where it left off last time.