Hi,

On Thu, 18 Oct 2007, Pete/Piet Delaney wrote:

quoted text
> Johannes:
>   I read somewhere in the past week that it was possible to maintain
>   our existing CVS environment with git. I though it was a separate
>   package to export git back to cvs but I just noticed a git-cvsserver
>   and as a std part of git and was wondering about using that.

Where did you read that?  AFAIK git-cvsserver is one option.  The other is 
cvsexportcommit.  The former is more appropriate if you want to switch the 
developers over to git, and want to provide a smooth path for the devs (or 
cannot convert a few hardcore CVS "fans").

The latter is appropriate if you cannot control the server side, or are 
not allowed to switch to CVS.

quoted text
> We have a number of build machines with flamebox perl scripts pulling 
> out CVS branches for builds. I was wondering what is the best way to use 
> git and it's nicer pull/push model and merge facility and possibly 
> maintain CVS exports for scripts doing builds if possible the cvsweb and 
> bonsai (CVS Query Form) that a number of engineers are currently using. 

I don't know how cvsweb copes with git-cvsserver, but I guess that there 
will be no problem.

quoted text
> I started looking over out flamebox scripts with the intent up 
> converting them over to git but I mentioned the git to cvs coexistence 
> and we are wondering if that's a better route than upgrading the 
> flamebox scripts. Having our existing cvsweb, bonsai, and gitweb along 
> with the git utilities seems at least desirable. Any thoughts or 
> suggestions?

My suggestion: if you're fine with CVS, stick with it.  Really.  I am not 
here to teach the whole world about the advantages of git, so by all 
means, if you yourself do not find any advantage to using git, don't use 
it.  Stick with what works for you.

Ciao,
Dscho

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html