Re: Caution when removing git branches - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Caution when removing git branches
Date
Msg-id 4D4155F60200002500039EA9@gw.wicourts.gov
Whole thread Raw
In response to Re: Caution when removing git branches  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Caution when removing git branches  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.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?
-Kevin


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Caution when removing git branches
Next
From: Robert Haas
Date:
Subject: Re: Spread checkpoint sync