[Savannah-hackers-public] Re: reliable, incremental git->cvs ?

[Sylvain Beucler]

On Mon, Nov 27, 2006 at 10:41:49PM +0100, Jim Meyering wrote:
> Hi Sylvain,
> 
> Do you know of a good way to sync a git repository to cvs?
> Ideally, it'd happen upon each commit or push, via a hook.
> 
> Currently I'm manually invoking a tiny script based on
> git-cvsexportcommit.  I think it's based om an example I saw in git's
> Documentation dir or in a man page.
> 
> Sylvain, in case you haven't been following bug-gnulib, we're planning to
> convert gnulib development from CVS to git.  But it doesn't always work.
> For example, it doesn't preserve executable bits on new files.  Yep,
> I need to fix and/or report that bug.  This is particularly relevant,
> because one of the conditions of switching gnulib, IMHO, must be to
> retain an automatically-up-to-date CVS repository.  That way, only
> developers who contribute regularly have to learn/use git.
> Everyone else can stick with CVS.

Hi,

Thanks for keeping me updated about this. Feel free to Cc:
address@hidden about this anytime.

I haven't investigated git<->cvs pipelines, so I don't have much to
say about it (do you mean uni- or bi-directional, btw?).

I saw this though:
http://www.kernel.org/pub/software/scm/git/docs/git-cvsserver.html

Apparently this gives
- a way to stick to the 'cvs' command-line when accessing a git repo
  (export CVS_SERVER=git-cvsserver)
- a way to access a git repo through the CVS pserver protocol
  (I'd need to attach that daemon to another IP because Savannah's git
  and cvs are on the same machine)

Could that help?

I can't guarantee I can set that up securely at Savannah but I can
investigate the tools some more if that can help.

-- 
Sylvain