Diff for "InstructionsforHgcvsimport"

Differences between revisions 3 and 6 (spanning 3 versions)

This page does not meet our wiki style guidelines. Please help improve this page by cleaning up its formatting.

This page is an incomplete stub. Please help improve this page by expanding it, following our wiki style guidelines.

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 6 as of 2012-05-13 09:56:58 → ⇥
  Size: 689
  Editor: 62
  Comment: Flag for style cleanup
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+<<Include(A:style)>>
<<Include(A:stub)>>
-Line 2:
+Line 5:
+{{{
-Line 4:
+Line 7:
+}}}
-Line 6:
+Line 9:
+{{{
-Line 8:
+Line 11:
-Line 10:
+Line 12:
-Line 12:
+Line 13:
+}}}
-Line 15:
+Line 16:
-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 18:
-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.