Importing from CVS issues

2005-08-16 Thread Alex Bennee
Hi, We've been having issues with CVS for some time and I thought I'd give git a spin. To do some like-for-like tests I'm having a go at importing our cvs repository into git so I can do some benchmarks on things like branch creation as well as play around with the visualisation tools. Obviously

Re: Importing from CVS issues

2005-08-16 Thread Martin Langhoff
I haven't seen this problem myself. There are some recent patches Junio merged that handle some oddities better. Give the 'pu' branch a go if you can. I take it that the repo is not public. I'd like to try and reproduce the problem. Can you get it to happen with a public repository? For

Re: Importing from CVS issues

2005-08-16 Thread David Kågedal
Alex Bennee [EMAIL PROTECTED] writes: Before the import script finally dies with: WARNING: revision 1.3.2.1 of file scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch DONE; creating master branch cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such file or

Re: Importing from CVS issues

2005-08-16 Thread Alex Bennee
On Tue, 2005-08-16 at 14:16 +0200, David Kågedal wrote: Alex Bennee [EMAIL PROTECTED] writes: Before the import script finally dies with: WARNING: revision 1.3.2.1 of file scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch DONE; creating master branch cp: cannot stat

Re: Importing from CVS issues

2005-08-16 Thread Alex Bennee
On Tue, 2005-08-16 at 23:26 +1200, Martin Langhoff wrote: I haven't seen this problem myself. There are some recent patches Junio merged that handle some oddities better. Give the 'pu' branch a go if you can. I'll look at that in a bit. I already picked up a few of the patches mentioned on the