| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Caution when removing git branches |
| Date: | 2011-01-27 17:28:37 |
| Message-ID: | AANLkTi=rA8tZqCGLTJ3vrwXe0UN5bzxPaOhytRLApzAx@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 27, 2011 at 12:24 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> So if someone does this (which does not look at all likely to me):
>>
>> git push origin :REL9_0_STABLE
>> git branch -r -D origin/REL9_0_STABLE
>> git branch -d REL9_0_STABLE
>>
>> ...then, yes, they will need to find someone who has run 'git
>> pull' since the last change that was made to that branch. OR they
>> could get it back from the anonymous mirror of the canonical
>> repository, which should always be up to date, OR I think there's
>> an automatically updated mirror on github also.
>
> I thought that git fsck by an administrator on the server would
> still show the original as a dangling commit, which could be checked
> out by the SHA1 ID. No?
That's yet another way of undoing it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-27 17:31:34 | Re: Caution when removing git branches |
| Previous Message | Robert Haas | 2011-01-27 17:27:44 | Re: Spread checkpoint sync |