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:07
Heya, git-stash in v1.7.0-rc0 gives me several hundred lines of : error: unable to find dd4a345a770f5c82a668932b7289f42b1ae38103 error: unable to find dd4a345a770f5c82a668932b7289f42b1ae38103 error: unable to find dd4a345a770f5c82a668932b7289f42b1ae38103 .... error: unable to find 0dc67edc22017de22161dde93baa615767b9c6e0 error: unable to find 0dc67edc22017de22161dde93baa615767b9c6e0 error: unable to find 0dc67edc22017de22161dde93baa615767b9c6e0 error: unable to find 0dc67edc22017de22161dde93baa615767b9c6e0 .... error: unable to find 980f084e71097df3d4086aaab574972321df80f2 error: unable to find 980f084e71097df3d4086aaab574972321df80f2 error: unable to find 980f084e71097df3d4086aaab574972321df80f2 error: unable to find 980f084e71097df3d4086aaab574972321df80f2 Other than that, it appears to work fine. 'git show <sha1>' works too - they're all a bunch of file contents, with no particular pattern. This only happens in my main (private) repo. I can't seem to come up with a reproducible example for anyone else... The previous build I was using - 5b15950ac414a8a2d4f5eb480712abcc9fe176d2 from Jan 19th - didn't show this problem. Want me to try and bisect further? -Jonathan