Re: Data Integrity & un-Commited Branches

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Data Integrity & un-Commited Branches

From: David Kastrup <hidden>
Date: 2016-06-15 22:43:34

"Nikodemus Siivola" [off-list ref] writes:
One thing that I've been bitten a couple of times is that
I think I'm on branch X, which should be clean, whereas
I'm really on branch Y with uncommitted changes. Then I
checkout another branch, and see the uncommitted work -- and
given that I have a couple of dozen related feature branches
in my tree it may take a while to figure which branch the
uncommitted work came from.
"Take a while"?  What's wrong with git-reflog?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Data Integrity & un-Commited Branches

From: Nikodemus Siivola <hidden>
Date: 2016-06-15 22:43:34

On 9/15/07, David Kastrup [off-list ref] wrote:
"Take a while"?  What's wrong with git-reflog?
Not needing it as a part of my regular workflow, and therefore
not thinking about it. *blush*

Cheers,

 -- Nikodemus
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help