summaryrefslogtreecommitdiff
path: root/Documentation/git-cvsimport-script.txt
AgeCommit message (Collapse)AuthorFilesLines
2005-08-17[PATCH] Add merge detection to git-cvsimportLibravatar Martin Langhoff1-1/+11
Added -m and -M flags for git-cvsimport to detect merge commits in cvs. While this trusts the commit message, in repositories where merge commits indicate 'merged from FOOBRANCH' the import works surprisingly well. Even if some merges from CVS are bogus or incomplete, the resulting branches are in better state to go forward (and merge) than without any merge detection. Signed-off-by: Martin Langhoff <martin.langhoff@gmail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-17[PATCH] Also handle CVS branches with a '/' in their nameLibravatar Johannes Schindelin1-1/+5
I track a CVS project which has a branch with a '/' in the branch name. Since git wants the branch name to be a file name at the same time, substitute that character to a '-' by default (override with "-s <subst>"). This should work well, despite the fact that a division and a difference are completely different :-) Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-16[PATCH] Add -k kill keyword expansion option to git-cvsimport - revisedLibravatar Martin Langhoff1-1/+6
Early versions of git-cvsimport defaulted to using preexisting keyword expansion settings. This change preserves compatibility with existing cvs imports and allows new repository migrations to kill keyword expansion. After exploration of the different -k modes in the cvs protocol, we use -kk which kills keyword expansion wherever possible. Against the protocol spec, -ko and -kb will sometimes expand keywords. Should improve our chances of detecting merges and reduce imported repository size. Signed-off: Martin Langhoff <martin.langhoff@gmail.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-08-16[PATCH] Fixed two bugs in git-cvsimport-script.Libravatar iso-8859-1?Q?David_K=E5gedal1-1/+8
The git-cvsimport-script had a copule of small bugs that prevented me from importing a big CVS repository. The first was that it didn't handle removed files with a multi-digit primary revision number. The second was that it was asking the CVS server for "F" messages, although they were not handled. I also updated the documentation for that script to correspond to actual flags. Signed-off-by: David K?5gedal <davidk@lysator.liu.se> Signed-off-by: Junio C Hamano <junkio@cox.net>
2005-07-11[PATCH] git-cvsimport-script: add "import only" optionLibravatar Sven Verdoolaege1-1/+6
git-cvsimport-script: add "import only" option which tells the script not to perform a checkout after importing. This ensures that the working directory and cache remain untouched and will not create them if they do not exist. Acked-by: Matthias Urlichs <smurf@smurf.noris.de> Signed-off-by: Sven Verdoolaege <skimo@kotnet.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-07-03Support :ext: access method.Libravatar Sven Verdoolaege1-1/+2
2005-07-03git-cvsimport-script: clean up documentationLibravatar Sven Verdoolaege1-8/+0
Remove documentation of irrelevant "type" option. Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
2005-07-03Make specification of CVS module to convert optional.Libravatar Sven Verdoolaege1-1/+1
If we're inside a checked out CVS repository, there is no need to explicitly specify the module as it is available in CVS/Repository. Also read CVS/Root if it's available and -d is not specified. Finally, explicitly pass root to cvsps as CVS/Root takes precedence over CVSROOT. Signed-off-by: Sven Verdoolaege <skimo@kotnet.org>
2005-07-03Fixed a typo in Documentation/git-cvsimport-script.txt.Libravatar Sven Verdoolaege1-1/+1
2005-06-30cvsimport: add documentation.Libravatar Matthias Urlichs1-0/+82