Re: Caution when removing git branches
| От | Robert Haas |
|---|---|
| Тема | Re: Caution when removing git branches |
| Дата | |
| Msg-id | AANLkTi=rA8tZqCGLTJ3vrwXe0UN5bzxPaOhytRLApzAx@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Caution when removing git branches ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Список | pgsql-hackers |
On Thu, Jan 27, 2011 at 12:24 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > 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? That's yet another way of undoing it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: