В сообщении от Воскресенье 17 Июль 2005 12:40 Wolfgang Denk написал(a): > Is there a way to make "git cvsimport" create branches in git for any > branches it encounters in the CVS repository? Heh. I was just preparing mail about the same problem. It seems that git-cvsimport-script really don't likes branches in CVS. I have attached simple script that demonstrates this. On my machine it gives: ============================= [EMAIL PROTECTED]:/tmp$ ./testscript cvs checkout: Updating project cvs add: scheduling file `a' for addition cvs add: use `cvs commit' to add this file permanently /tmp/20050717125452/cvsroot/project/a,v <-- a initial revision: 1.1 cvs tag: Tagging . T a /tmp/20050717125452/cvsroot/project/a,v <-- a new revision: 1.2; previous revision: 1.1 cvs update: Updating . U a /tmp/20050717125452/cvsroot/project/a,v <-- a new revision: 1.1.2.1; previous revision: 1.1 cvs rlog: Logging project New a: 2 bytes. Tree ID 2ce1eef76631e82282e0f7f0cf9e6f3e9a4a0b1e Committed patch 1 (origin) Committing initial tree 2ce1eef76631e82282e0f7f0cf9e6f3e9a4a0b1e Commit ID f7030e1c361f94b8847ef6ad88248a675c7ce5a9 Update a: 4 bytes. Tree ID 9d3d025fff2e43c6a7b837056632b436c8e31dfe Parent ID f7030e1c361f94b8847ef6ad88248a675c7ce5a9 Committed patch 2 (origin) Commit ID 67889434ca9623ad91f8e81e6143fed9c4115a86 Switching from origin to branch1 usage: git-read-tree (<sha> | -m [-u] <sha1> [<sha2> [<sha3>]]) read-tree failed: 256 [EMAIL PROTECTED]:/tmp$ ============================= Is it a planned behaivoir or cvsimport script were just recently broken?
-- Respectfully Alexey Nezhdanov
#!/bin/sh dirname=`date +"%Y%m%d%H%M%S"` mkdir /tmp/$dirname cd /tmp/$dirname mkdir cvsroot declare -x CVSROOT=/tmp/$dirname/cvsroot cvs init mkdir cvsroot/project cvs co project cd project echo 1 >a cvs add a cvs ci -m 1 a cvs tag -b branch1 echo 2 >>a cvs ci -m 2 a cvs update -r branch1 echo 3 >>a cvs ci -m 3 a git-cvsimport-script -v
