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

Re: marking old branches as no longer maintained

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(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 21:05:10
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

On 06/28/2011 04:51 PM, Peter Eisentraut wrote:
> 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.

No, not really. I'd use 'git ls-tree $branchname $filetolookfor". I have 
tested it and this works just fine, takes a second or so.

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

As I told Magnus, that gets ugly because of limitations in MinGW's SDK 
perl. I suppose I could just not implement the feature for MinGW, but 
I've tried damn hard not to make those sorts of compromises and I'm not 
keen to start.



In response to


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2011-06-28 21:31:35
Subject: Re: marking old branches as no longer maintained
Previous:From: Nicolas BarbierDate: 2011-06-28 20:52:20
Subject: Re: SSI modularity questions

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