Re: "git pull" throws away dirty state

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mar 16, 2008, 18:24 UTC
Message-ID: <alpine.LFD.1.00.0803161123260.3020@woody.linux-foundation.org>
In-Reply-To: <alpine.LFD.1.00.0803161055510.3020@woody.linux-foundation.org>

On Sun, 16 Mar 2008, Linus Torvalds wrote:

Show 5 quoted lines

> 
> Ok, this is distressing, and I suspect it's another bug of mine due to 
> unpack-trees changes, but before I delve into it deeper I thought I'd 
> report it here and see if others see it too, and maybe it's due to 
> something else..

Nope, I bisected it down to

	34110cd4e394e3f92c01a4709689b384c34645d8 is first bad commit

	Make 'unpack_trees()' have a separate source and destination index

and I'm trying to figure out what part of that triggered this bug.

		Linus