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

Re: Caution when removing git branches

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "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:24:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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?

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2011-01-27 17:27:44
Subject: Re: Spread checkpoint sync
Previous:From: Magnus HaganderDate: 2011-01-27 17:23:51
Subject: Re: Caution when removing git branches

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