Skip site navigation (1) Skip section navigation (2)

Re: marking old branches as no longer maintained

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: marking old branches as no longer maintained
Date: 2011-06-28 20:51:26
Message-ID: 1309294287.30757.1.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On tis, 2011-06-28 at 15:37 -0400, Andrew Dunstan wrote:
> What I'd like to do is to allow this to read:
> 
>     if ($branch eq 'global')
>     {
>          $conf{branches_to_build} = 'ALL';
>     }
> 
> and have it choose the right set for you.

It seems to me that if you put a marker file into old branches, you'd
still have to check out and poll the old branches, which could become
somewhat expensive as the number of old branches grows.

Couldn't you just put a text file on the build farm server with
recommended branches?


In response to

Responses

pgsql-hackers by date

Next:From: Nicolas BarbierDate: 2011-06-28 20:52:20
Subject: Re: SSI modularity questions
Previous:From: Pavel StehuleDate: 2011-06-28 20:28:21
Subject: Re: Fwd: Keywords in pg_hba.conf should be field-specific

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group