| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2011-01-27 17:23:17 | Re: ALTER TYPE 3: add facility to identify further no-work cases |
| Previous Message | Robert Haas | 2011-01-27 17:19:17 | Re: Caution when removing git branches |