From c20b767eca1980d15697f0a7a6e6e728f819a3ab Mon Sep 17 00:00:00 2001 From: mhagger Date: Mon, 3 Feb 2014 12:52:37 +0000 Subject: [PATCH] Update cvs2git.html. git-svn-id: http://cvs2svn.tigris.org/svn/cvs2svn/trunk@5448 be7e6eca-30d4-0310-a8e5-ac0d63af7087 --- www/cvs2git.html | 72 ++++++++++++++++++++++++++++++-------------------------- 1 file changed, 39 insertions(+), 33 deletions(-) diff --git a/www/cvs2git.html b/www/cvs2git.html index c4fc594a..503a08a0 100644 --- a/www/cvs2git.html +++ b/www/cvs2git.html @@ -111,18 +111,17 @@ href="http://www.kernel.org/pub/software/scm/git/docs/git fast-import.html">git fast-import tool.

Although cvs2git is considerably newer than cvs2svn, and much less -well tested, it is believed that cvs2git can (cautiously) be used for -production conversions. If you use cvs2git, please let us know how it -worked for you!

+well tested, it is believed that cvs2git can be used for production +conversions. If you use cvs2git, please let us know how it worked for +you!

cvs2git limitations

-

cvs2git still has many limitations compared to cvs2svn. The main -cvs2svn developer has limited git experience and very limited time, so -help would be much appreciated! Some of these missing -features would be pretty easy to program, and I'd be happy to help you -get started.

+

cvs2git still has many limitations compared to +cvs2svn. Help would be much appreciated! Some of +these missing features would be pretty easy to program, and I'd be +happy to help you get started.

-

This creates two output files in git - fast-import format. The names of these files are specified by - your options file or command-line arguments. In the example, - these files are named cvs2git-tmp/git-blob.dat and - cvs2git-tmp/git-dump.dat.

+

This creates two output files + in git + fast-import format. The names of these files are specified + by your options file or command-line arguments. In the example, + these files are named cvs2git-tmp/git-blob.dat and + cvs2git-tmp/git-dump.dat.

@@ -342,9 +340,8 @@ cvs2git --options=OPTIONS-FILE

Initialize a git repository:

-mkdir myproject.git
-cd myproject.git
-git init --bare
+git init --bare /path/to/myproject.git
+cd /path/to/myproject.git
 
@@ -355,8 +352,8 @@ git init --bare fast-import:

-git fast-import --export-marks=../cvs2git-tmp/git-marks.dat < ../cvs2git-tmp/git-blob.dat
-git fast-import --import-marks=../cvs2git-tmp/git-marks.dat < ../cvs2git-tmp/git-dump.dat
+git fast-import --export-marks=../cvs2git-tmp/git-marks.dat <../cvs2git-tmp/git-blob.dat
+git fast-import --import-marks=../cvs2git-tmp/git-marks.dat <../cvs2git-tmp/git-dump.dat
 

On Linux/Unix this can be shortened to:

@@ -369,6 +366,16 @@ cat ../cvs2git-tmp/git-blob.dat ../cvs2git-tmp/git-dump.dat | git fast-import
  • +

    Delete the TAG.FIXUP branch:

    + +
    +git branch -D TAG.FIXUP
    +
    + +
  • + +
  • +

    (Optional) View the results of the conversion, for example:

    @@ -416,27 +423,26 @@ cd myproject
     

    Converting to a non-bare repository

    If you want to convert into a non-bare git repository (one - including a working tree), then you need to make two changes to the - above procedure:

    + that includes a working tree), then you need to make two changes to + the above procedure:

    • Omit the --bare option in step 4; i.e., type

      -mkdir myproject.git
      -cd myproject.git
      -git init
      +git init /path/to/myproject.git
      +cd /path/to/myproject.git
       
    • When the conversion is done, instead of cloning as described - in step 9, you need to explicitly check out the "master" version + in step 10, you need to explicitly check out the "master" version of the files into your working tree:

      -git checkout
      +git checkout master
       
    • -- 2.11.4.GIT