Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Date
Msg-id 1309359758-sup-6813@alvh.no-ip.org
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
List pgsql-hackers
Excerpts from Magnus Hagander's message of mié jun 29 10:30:51 -0400 2011:
> On Tue, Jun 28, 2011 at 19:45, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
> > Excerpts from Tom Lane's message of mar jun 28 10:39:22 -0400 2011:
> >
> >> I think it would be sensible to block branch removal, as there's
> >> basically never a scenario where we'd do that during current usage.
> >> I'm not excited about blocking branch addition, although I worry
> >> sooner or later somebody will accidentally push a private development
> >> branch :-(.  Is it possible to block only removal and not addition?
> >
> > If we can tweak the thing, how about we only allow creating branches
> > that match a certain pattern, say ^REL_\d+_\d+_STABLE$?
> 
> I've put this in place - except I used ^REL\d+... and not what you
> suggested, since that's how we name our branches :P

Hah!  It took me a while to notice the difference :-D

Thanks!  I know I feel safer with this in place :-P

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Next
From: Merlin Moncure
Date:
Subject: Re: Process local hint bit cache