From: picca <picca@synchrotron-soleil.fr>
Date: Fri, 08 Jun 2007 13:42:22 GMT
Subject: interaction between cvsimport and cvsexportcommit
Message-ID: <20070608154222.56870830@localhost.localdomain>

Hello

In the institut where I am working www.synchrotron-soleil.fr, the
"computing department" use CVS for all their projects. As I am not from
this department (I am a scientist), I can use my own tools and git is
one of them.
Nevertheless I need to interact with them (I am writting a C++
library to control diffractometers) so I use cvsimport and
cvsexportcommit.

The point is that I find this over complicate compare to my git
day-to-day experience.

I do not understand why cvsimport and cvsexportcommit do not
interact nicelly to ease git <-> cvs.
For example as a neeby I expect this to work out of the box
after the first cvsimport

git cvsimport
do some work
git commit -a
git cvsexportcommit

and that's all

Instead of this we have this:

$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git-cvsexportcommit -v <commit-sha1>
$ cvs commit -F .mgs <files>

or even worse

$ export GIT_DIR=~/project/.git
$ cd ~/project_cvs_checkout
$ git-cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1
git-cvsexportcommit -c -p -v


what is missing in cvsexportcommit and cvsimport to lower the git <->
cvs barrier.

Thank you.

Frederic

PS: Sorry for my poor english.