| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed |
| Date: | 2011-06-28 17:45:33 |
| Message-ID: | 1309283047-sup-4326@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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$?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-06-28 19:59:45 | pgsql: Modernise pg_hba.conf token processing |
| Previous Message | Magnus Hagander | 2011-06-28 16:47:33 | Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-06-28 17:46:22 | marking old branches as no longer maintained |
| Previous Message | Alvaro Herrera | 2011-06-28 17:26:23 | Re: Word-smithing doc changes |