[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 5099 - staging broken?
From: |
David Kastrup |
Subject: |
Re: Issue 5099 - staging broken? |
Date: |
Sun, 26 Mar 2017 10:17:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Thomas Morley <address@hidden> writes:
> accidently I permanently deleted the branch where the patch for issue
> 5099 was.
That would be a rather difficult feat (you don't do things like that
"accidentally" with Git since you have to work very hard to do them,
with a set of very explicit commands unless you are going to wait for
several months as part of the recipe).
Try
git reflog
and write down the hash for the first occurence of your branch in the
list (which would be last in time).
Then do
git branch hash-that-you-wrote-down
and the branch is back in life. Of course, since this will be an
unpublished branch, you have to do this in the repository where you
"permanently" deleted the branch.
Git tends to keep "permanently deleted" stuff around for 3 months or so
before it really removes them for good.
--
David Kastrup
- Issue 5099 - staging broken?, James, 2017/03/25
- Re: Issue 5099 - staging broken?, Thomas Morley, 2017/03/25
- Re: Issue 5099 - staging broken?, David Kastrup, 2017/03/26
- Re: Issue 5099 - staging broken?, Thomas Morley, 2017/03/26
- Re: Issue 5099 - staging broken?, David Kastrup, 2017/03/26
- Re: Issue 5099 - staging broken?, Thomas Morley, 2017/03/26
- Re: Issue 5099 - staging broken?, David Kastrup, 2017/03/26
- Re: Issue 5099 - staging broken?, Thomas Morley, 2017/03/26
- Re: Issue 5099 - staging broken?, James, 2017/03/26
Re: Issue 5099 - staging broken?,
David Kastrup <=