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: Jim Meyering
Subject: Re: [Savannah-hackers-public] Re: savannah shell access?
Date: Sat, 06 Jan 2007 14:01:59 +0100

Sylvain Beucler <address@hidden> wrote:
...
>> 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),

It's easy to recreate.  Just check out from cvs.

The hook could theoretically check out a copy of the cvs module for each
git push, apply and commit the pushed change sets, and then remove it
when done.  However, I've preferred to maintain a clean, checked-out
directory in a known location and use that.  Far less overhead.

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




reply via email to

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