Fwd: Fwd: git cvsimport implications

MIchael, sorry for dup - didn't press reply all for the first one.

1. You are making assumptions and conclusions that have no grounds.
I asked for help understanding what are the problems of cvsimport.
Never i said i'm not willing use cvs2git. Never i said I'm happy to have
problems in my git repos. So, this "low standard" punch was... not necessary.

2. I started to use cvsimport because it was the tool *provided with
git* about three years ago.
By that time i didn't find any better and simpler tool to use and
those implications were uknown for me,
they were brought up to my attention just recently.
CVS is not good for branches, so most of our projects didn't have any
cvs branches.
So for majority of those it seems that the cvsimport did it's job just fine.
Now we are going to try to migrate some projects that are using CVS
branches heavily.
That concerns me, so i'm looking for better tool.

3. Is there a way to have the whole plumbing with the
blobfiles and dumpfiles and consequent git fast-import wrapped into
nice command like:

git cvsimport -C path/to/my/new/shiny/gitrepo

Or are there any particular reasons why end user must deal with blob and dump files and do fast-import afterwards?

Thanks, Eugene