Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash
From: Jonathan del Strother <hidden>
Date: 2016-06-15 22:48:08
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash · Junio C Hamano <hidden>
- 2016-06-15 · Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash · Junio C Hamano <hidden>
- 2016-06-15 · Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash · Jonathan del Strother <hidden>
- 2016-06-15 · Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash · Junio C Hamano <hidden>
- 2016-06-15 · Re: v1.7.0-rc0 shows lots of "unable to find <sha1>" on git-stash · Jonathan del Strother <hidden>
On 29 January 2010 17:44, Junio C Hamano [off-list ref] wrote:
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.