summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 66e631d)
raw | patch | inline | side by side (parent: 66e631d)
author | Junio C Hamano <junkio@cox.net> | |
Sat, 16 Jul 2005 03:54:04 +0000 (20:54 -0700) | ||
committer | Linus Torvalds <torvalds@g5.osdl.org> | |
Sat, 16 Jul 2005 04:53:22 +0000 (21:53 -0700) |
The cvsimport example in the cvs migration document was still
using the old syntax for target repository after new and
improved cvsimport-script was merged.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
using the old syntax for target repository after new and
improved cvsimport-script was merged.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Documentation/cvs-migration.txt | patch | blob | history |
index e39b82938a98dbd258f534c4cadccd6de4db7888..a4d4b7e8789e58470a0740a7aca179db61361ee9 100644 (file)
any more familiar with it, but make sure it is in your path. After that,
the magic command line is
- git cvsimport -v -d <cvsroot> <module> <destination>
+ git cvsimport -v -d <cvsroot> -C <destination> <module>
which will do exactly what you'd think it does: it will create a git
archive of the named CVS module. The new archive will be created in the