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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-hackers by date

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