Re: Git cvsserver serious issue - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Git cvsserver serious issue
Date
Msg-id AANLkTikhyss_vw+nGosGPR+mtSQ_M_wKDUnV9vFoMn07@mail.gmail.com
Whole thread Raw
In response to Re: Git cvsserver serious issue  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Git cvsserver serious issue
List pgsql-hackers
On Fri, Oct 8, 2010 at 3:13 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> On 10/08/2010 02:09 AM, Magnus Hagander wrote:
>> On Fri, Oct 8, 2010 at 03:52, Andrew Dunstan<andrew@dunslane.net>  wrote:
>>> There's a simpler solution which I have just tested. Instead of patching,
>>> use the Pg driver instead of SQLite. Set the dbname to %m. If the
>>> database
>>> doesn't exist the cvs checkout will fail. So we just set up databases for
>>> the modules we want to export (master and RELn_m_STABLE for the live
>>> branches).

Wouldn't it be simpler be to generate hourly tarball on some host and wget it?
It can be generated even more often, as no history need to be kept.

Considering the state of cvsserver, can you be certain that whatever
is coming from it is really the most recent code?

--
marko


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: standby registration (was: is sync rep stalled?)
Next
From: Andrew Dunstan
Date:
Subject: Re: Git cvsserver serious issue