Re: Data Integrity & un-Commited Branches

From: David Kastrup <dak@gnu.org>
Date: Sep 15, 2007, 13:59 UTC
Message-ID: <85myvoav1g.fsf@lola.goethe.zz>
In-Reply-To: <6bcc356f0709150611i97d31f0yb91016e53c4f5e9f@mail.gmail.com>

"Nikodemus Siivola" <nikodemus@random-state.net> writes:

Show 7 quoted lines

> 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