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

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

Re: [Savannah-hackers-public] Re: savannah shell access?


From: Sylvain Beucler
Subject: Re: [Savannah-hackers-public] Re: savannah shell access?
Date: Sat, 6 Jan 2007 12:16:21 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

On Sat, Jan 06, 2007 at 11:59:29AM +0100, Jim Meyering wrote:
> Sylvain Beucler <address@hidden> wrote:
> > You need to enter the vserver first:
> > $ vserver cvs enter
> >
> > The cron file is /etc/cron.d/rsync_external_cvs_repositories
> >
> > Files are otherwise directly accessible from /vservers/cvs/.
> 
> Thanks!
> I've turned off the pull of cvs-coreutils from proulx.com.
> 
> Now for a policy question:
> 
> In order to set up a git->cvs mirror, I need to maintain a
> cvs-checked-out copy of the coreutils module (eventually gnulib, too).
> It must be accessible by the git update hook, to be used whenever
> someone does a "git-push" to sv.gnu.org.
> 
> For now, I'm using /var/tmp/git-to-cvs, but it's trivial to change.

I think that depends how your hooks depend on it:

- if they recreate it as needed, /var/tmp sound good. Maybe /tmp is
better because it's in ramfs

- if they can't recreate it, maybe we need to place it somewhere that
is backed-up (/var/lib/git/sthing),

- or maybe we need to recreate/repopulate the directories at boot time
(like the cvs locks dirs)

-- 
Sylvain




reply via email to

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