Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
От | Magnus Hagander |
---|---|
Тема | Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed |
Дата | |
Msg-id | BANLkTikkMMPBW_EnjnysHv_MAnyfjtasJg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed
Re: [COMMITTERS] pgsql: Branch refs/heads/REL9_1_STABLE was removed |
Список | pgsql-hackers |
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 I'm going to push an actual valid branch, let's say 9.7, and then remove it again, just to make sure things worked (with it installed I cannot push an invalid branch, so i can't test the branch removal block). So don't panic if you see that one :) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: