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

From Andrew Dunstan
Subject Re: Git cvsserver serious issue
Date
Msg-id 4CB4CE00.5070105@dunslane.net
Whole thread Raw
In response to Re: Git cvsserver serious issue  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers

On 10/12/2010 03:57 PM, Magnus Hagander 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).
>>
>> A database per branch seems like a horrible idea in general, but if it
>> works us around the bug, it seems like a doable idea.. As long as
>> we'll never have a branch called "postgres" or "git" (already in use
>> on that box).
>>
>> I'll look into it.
> Should be up and working now. master branch is ready, working on
> prepping rel9_0_stable.
>
> CVSROOT is :pserver:anonymous@git.postgresql.org:/postgresql.git
>
> module name is master or REL9_0_STABLE. master available now,
> rel_9_0_stable sohuld be available in about half an hour.


Thanks for this.

I have tested it (see 
<http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=quoll&dt=2010-10-12%2019:55:03>) 
and there is a new Release of the buildfarm client to support its use: 
see <http://pgfoundry.org/frs/?group_id=1000040>

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: host name support in pg_hba.conf
Next
From: Andrew Dunstan
Date:
Subject: Re: SQL command to edit postgresql.conf, with comments