Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash

On 30 January 2010 12:31, Jens Lehmann [off-list ref] wrote:

Am 30.01.2010 01:46, schrieb Jonathan del Strother:

quoted

On 29 January 2010 17:44, Junio C Hamano [off-list ref] wrote:

quoted

Jonathan del Strother [off-list ref] writes:

quoted

Heya,

git-stash in v1.7.0-rc0 gives me several hundred lines of :
The previous build I was using -
5b15950ac414a8a2d4f5eb480712abcc9fe176d2 from Jan 19th - didn't show
this problem.  Want me to try and bisect further?

Yes, please.

ee6fc514f2df821c2719cc49499a56ef2fb136b0 (Show submodules as modified
when they contain a dirty work tree) seems to be the first bad commit.

Thanks for pinning that down.

I assume you have one or more submodules, maybe even with untracked
or yet uncommitted modified files in your tree? If so, what does git
status say in the superproject and in the submodule(s)?

Yep, I have 10 submodules.  However, they're all completely clean with
no tracked or untracked changes shown in git status.  Anything else I
can investigate?