Hi Sylvain,
As you know, we want to convert gnulib to use git soon. I'd like
to use coreutils as a testbed for that. Currently, the coreutils
master repo is a git one. I manually run a script to mirror its
changes to a cvs repo on my local system. Then, I rsync that
repo to Bob's system (proulx.com) from which Savannah regularly
rsync-pulls updates to keep the Savannah coreutils CVS repository
up to date. These contortions are because I don't allow inbound
rsync access to my development systems, and back when we set
this up, that was the only other way to update such a repository.
I'd like to change things so that whenever I git-push a new
coreutils change-set to Savannah, a git update hook will mirror
that change into the CVS repository on Savannah. I've done
experiments already, and my modified .git/hook/update script
does the job just fine.
Here are some of the things needed to accomplish this:
- a directory on git.sv.gnu.org in which to keep a cvs-checked-out
copy of coreutils (this is a prerequisite because my implementation
uses git-cvsexportcommit). A cvs coreutils checkout requires
less than 10MB.
- I suppose that directory should have sticky-group perms allowing
write by people with coreutils push access.
- coordinate these two steps:
* stop the coreutils-rsync from proulx.com
* enable the git->cvs hook
Does that sound workable?
Finally, is there a place on Savannah where files like this update
hook script are version controlled?
Happy holidays!
Jim
