Re: [HACKERS] marking old branches as no longer maintained

2011-07-12 Thread Magnus Hagander
On Tue, Jul 12, 2011 at 01:10, Andrew Dunstan wrote: > > > On 07/11/2011 07:59 PM, Bruce Momjian wrote: >> >> Andrew Dunstan wrote: >>> >>> On 06/28/2011 05:31 PM, Peter Eisentraut wrote: On tis, 2011-06-28 at 17:05 -0400, Andrew Dunstan wrote: >> >> Couldn't you just put a text

Re: [HACKERS] marking old branches as no longer maintained

2011-07-11 Thread Andrew Dunstan
On 07/11/2011 07:59 PM, Bruce Momjian wrote: Andrew Dunstan wrote: On 06/28/2011 05:31 PM, Peter Eisentraut wrote: On tis, 2011-06-28 at 17:05 -0400, Andrew Dunstan wrote: Couldn't you just put a text file on the build farm server with recommended branches? As I told Magnus, that gets ugly

Re: [HACKERS] marking old branches as no longer maintained

2011-07-11 Thread Bruce Momjian
Andrew Dunstan wrote: > > > On 06/28/2011 05:31 PM, Peter Eisentraut wrote: > > On tis, 2011-06-28 at 17:05 -0400, Andrew Dunstan wrote: > >>> 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 i

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
On 06/28/2011 05:31 PM, Peter Eisentraut wrote: On tis, 2011-06-28 at 17:05 -0400, Andrew Dunstan wrote: 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 no

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Peter Eisentraut
On tis, 2011-06-28 at 17:05 -0400, Andrew Dunstan wrote: > > 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

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
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 t

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Peter Eisentraut
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 o

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
On 06/28/2011 03:48 PM, Dave Page wrote: But if you want to run some more frequently you'd still be stuck having to manage that yourself. There's actually not a lot of point in doing it that way, though. We don't build unless there have been changes on the branch, unless told otherwise, so

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Dave Page
On Tuesday, June 28, 2011, Andrew Dunstan wrote: > > > On 06/28/2011 03:17 PM, Dave Page wrote: > > On Tue, Jun 28, 2011 at 8:02 PM, Magnus Hagander  wrote: > > If we can find a good way to do it, I think having BF animals > automatically picking up new branches is a very good thing to have. So >

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
On 06/28/2011 03:17 PM, Dave Page wrote: On Tue, Jun 28, 2011 at 8:02 PM, Magnus Hagander wrote: If we can find a good way to do it, I think having BF animals automatically picking up new branches is a very good thing to have. So don't give up so easily :D If adding a more or less random file

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
On 06/28/2011 03:02 PM, Magnus Hagander wrote: If it's contentious I won't bother. We've managed OK for years, and can go on managing as we are. If we can find a good way to do it, I think having BF animals automatically picking up new branches is a very good thing to have. So don't give up

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Dave Page
On Tue, Jun 28, 2011 at 8:02 PM, Magnus Hagander wrote: > > If we can find a good way to do it, I think having BF animals > automatically picking up new branches is a very good thing to have. So > don't give up so easily :D If adding a more or less random file to > back branches is the only way to

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Magnus Hagander
On Tue, Jun 28, 2011 at 20:38, Andrew Dunstan wrote: > > > On 06/28/2011 01:54 PM, Magnus Hagander wrote: >> >> On Tue, Jun 28, 2011 at 19:46, Andrew Dunstan  wrote: >>> >>> I'd like to add a feature to the buildfarm that automatically picks up >>> any >>> new branch and automatically stops buildi

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
On 06/28/2011 01:54 PM, Magnus Hagander wrote: On Tue, Jun 28, 2011 at 19:46, Andrew Dunstan wrote: I'd like to add a feature to the buildfarm that automatically picks up any new branch and automatically stops building any branch we're not maintaining any more. To do the latter, I need some w

Re: [HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Magnus Hagander
On Tue, Jun 28, 2011 at 19:46, Andrew Dunstan wrote: > > I'd like to add a feature to the buildfarm that automatically picks up any > new branch and automatically stops building any branch we're not maintaining > any more. To do the latter, I need some way for the client to detect that we > are or

[HACKERS] marking old branches as no longer maintained

2011-06-28 Thread Andrew Dunstan
I'd like to add a feature to the buildfarm that automatically picks up any new branch and automatically stops building any branch we're not maintaining any more. To do the latter, I need some way for the client to detect that we are or aren't interested in a branch. What I'd like to do is add