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 17:22:26
Message-ID: 201101271722.p0RHMQu22721@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas wrote:
> The master branch can be removed the same as any other one - just
> substitute master in place of REL9_0_STABLE in the above commands.
> But why would you do such a nutty thing?  Worst case scenario looks to
> me like you type the first of those commands and then go "oh crud".
> And if any of our 19 committers were unaware of the hazards of
> inserting random colons into their git commands, hopefully this
  -----------------------------------------------
> discussion has awakened them to the error of their ways.

Yes, that was really my goal --- to point out that some git operations
are not reverable.

-- 
  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: Noah MischDate: 2011-01-27 17:23:17
Subject: Re: ALTER TYPE 3: add facility to identify furtherno-work cases
Previous:From: Robert HaasDate: 2011-01-27 17:19:17
Subject: Re: Caution when removing git branches

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