summaryrefslogtreecommitdiffstats
path: root/git-cvsimport.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2009-03-25 18:49:30 +0000
committerJunio C Hamano <junio@hera.kernel.org>2009-03-25 18:49:30 +0000
commit625716ad62c5c0b2c57c90079944a7f6b914bb09 (patch)
tree14a7d93a4f8faf9f5bc601b6f523d95def468bd1 /git-cvsimport.txt
parent883263c41344dbf227ae55c51f7430086a2ea540 (diff)
downloadgit-htmldocs-625716ad62c5c0b2c57c90079944a7f6b914bb09.tar.gz
Autogenerated HTML docs for v1.6.2.1-345-g89fb
Diffstat (limited to 'git-cvsimport.txt')
-rw-r--r--git-cvsimport.txt34
1 files changed, 34 insertions, 0 deletions
diff --git a/git-cvsimport.txt b/git-cvsimport.txt
index b7a8c10b8..31237259e 100644
--- a/git-cvsimport.txt
+++ b/git-cvsimport.txt
@@ -24,6 +24,9 @@ repository, or incrementally import into an existing one.
Splitting the CVS log into patch sets is done by 'cvsps'.
At least version 2.1 is required.
+*WARNING:* for certain situations the import leads to incorrect results.
+Please see the section <<issues,ISSUES>> for further reference.
+
You should *never* do any work of your own on the branches that are
created by 'git-cvsimport'. By default initial import will create and populate a
"master" branch from the CVS repository's main branch which you're free
@@ -164,6 +167,37 @@ If '-v' is specified, the script reports what it is doing.
Otherwise, success is indicated the Unix way, i.e. by simply exiting with
a zero exit status.
+[[issues]]
+ISSUES
+------
+Problems related to timestamps:
+
+ * If timestamps of commits in the cvs repository are not stable enough
+ to be used for ordering commits
+ * If any files were ever "cvs import"ed more than once (e.g., import of
+ more than one vendor release)
+ * If the timestamp order of different files cross the revision order
+ within the commit matching time window
+
+Problems related to branches:
+
+ * Branches on which no commits have been made are not imported
+ * All files from the branching point are added to a branch even if
+ never added in cvs
+ * files added to the source branch *after* a daughter branch was
+ created: If previously no commit was made on the daugther branch they
+ will erroneously be added to the daughter branch in git
+
+Problems related to tags:
+
+* Multiple tags on the same revision are not imported
+
+If you suspect that any of these issues may apply to the repository you
+want to import consider using these alternative tools which proved to be
+more stable in practise:
+
+* cvs2git (part of cvs2svn), `http://cvs2svn.tigris.org`
+* parsecvs, `http://cgit.freedesktop.org/~keithp/parsecvs`
Author
------