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

From Michael Paquier
Subject Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Date
Msg-id BANLkTikrARi_187aGxQGpt7KwheRF1M=EA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers

On Thu, Jun 30, 2011 at 12:03 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
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
Thanks, +10.
This is cool and will avoid for sure future problems.

--
Michael Paquier
http://michael.otacoo.com

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Adding Japanese README
Next
From: Joe Conway
Date:
Subject: SECURITY LABEL on shared database object