savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers-public] Re: Overwriting bare repositories' master


From: Han-Wen Nienhuys
Subject: [Savannah-hackers-public] Re: Overwriting bare repositories' master
Date: Mon, 30 Oct 2006 23:47:39 +0100
User-agent: Thunderbird 1.5.0.7 (X11/20061008)

Sylvain Beucler escreveu:
Hi,

On Mon, Oct 30, 2006 at 06:55:34PM +0100, Han-Wen Nienhuys wrote:
Sylvain Beucler escreveu:
Hello,

I'm trying to setup a git hosting facility, such as repo.or.cz. The
facility provides a pre-initialized git repository only accessible
through git-shell.
repo_one$ git push
address@hidden:/srv/git/sources/administration.git \
  master:refs/heads/master

Does this mean that we will get GIT support on savannah? Cool!

We're experimenting with GIT for GNU LilyPond, so it would be really nice to have distributed VC with minimum fuss.

Cool. Do you want to create a repository for lilypond now? I can
create one; it is temporarily at http://cvs.sv.gnu.org/gitweb/ .

Does this already work with the savannah project memberships system?

Beware, that's a ZETA service ;)

There is no real hurry; we're making do with repo.or.cz and lilypond.org currently. But if there is a some sort fo regular system in place, I think we wouldn't mind being one of the first to go to a DVC.

Also, Jan and I are still having some quarrels on which distributed VC we should standardize on (Jan being fan of bzr, and me of git -- we haven't evaluated hg yet.) Are you planning to support just git, or are others on the horizon too?

If you introduce GIT on savannah, it might be a nice idea to import all of the 'live' CVS repositories automatically into a branch of a per-project/per-module GIT repository. Importing a sizable CVS repo actually takes quite a lot of time, so having the imports done already makes it a lot easier to experiment for people.

That sounds good. It will probably takes days, because there're lots
of repos, and SV is already a loaded machine, but automatic conversion
sounds very good.

It will take a long time, so maybe it's better to do this on request. I recall that my machine (core duo 1.6ghz) chugged for several hours converting the lilypond repository.

It may be difficult to keep a GIT repository in sync with CVS until
people actually start using it. Did you already try a repository
conversion? Can this be done?

Keeping GIT updated with CVS is fairly easy. For lilypond, we have an hourly cron that does a cvsimport. It does run a

  cvs rlog

getting info from the entire repository at savannah, but then it only pulls in the new changes.

The headaches start when you want to merge changes from GIT back into CVS, but that can't be automated anyway.

--
 Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen




reply via email to

[Prev in Thread] Current Thread [Next in Thread]