Skip site navigation (1) Skip section navigation (2)

Re: Caution when removing git branches

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Caution when removing git branches
Date: 2011-01-27 16:52:21
Message-ID: 201101271652.p0RGqLn12570@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas wrote:
> On Thu, Jan 27, 2011 at 11:41 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> Or for that we could just disable branch creation *completely*, and
> >> then turn off that restriction that one time / year that we actually
> >> create a branch?
> >
> > Well, branch creation can always be undone --- branch removal seems like
> > the big problem because it can't.
> 
> As I've repeatedly said, branch removal CAN be undone.  I don't see
> any evidence that we have an actual problem here that needs worrying
> about.

OK, someone removes a branch.  If it is still in his local tree, he can
push it back.  If not, he has to go around and find someone who does
have it, and who has the most recent copy?  Can master be removed too?

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-01-27 17:06:26
Subject: Re: Caution when removing git branches
Previous:From: Robert HaasDate: 2011-01-27 16:44:46
Subject: Re: Caution when removing git branches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group