Just a quick report since I don't have time to bisect now (will do later
if no other gitster is faster...)
When I execute the below script 'git show' crashes. 'git log --oneline -2' gives
for example:
3808bade5b76c4663ac4a3f751dc9f1ed0b08f2e three
error: Could not read
Am 25.09.2013 16:47, schrieb Stefan Näwe:
Just a quick report since I don't have time to bisect now (will do later
if no other gitster is faster...)
Seems to be somewhere between v1.8.3.1 (OK) and v1.8.3.2 (not OK) !!
When I execute the below script 'git show' crashes. 'git log --oneline
Am 25.09.2013 16:47, schrieb Stefan Näwe:
Just a quick report since I don't have time to bisect now (will do later
if no other gitster is faster...)
I'd marry 'git bisect' if I wasn't already... ;-)
This is what it gives me if I use my script (slightly modified to also run make)
with 'git
Stefan Näwe stefan.naewe at atlas-elektronik.com writes:
Am 25.09.2013 16:47, schrieb Stefan Näwe:
This is what it gives me if I use my script (slightly modified
to also run make) with 'git bisect run':
6035d6aad8ca11954c0d7821f6f3e7c047039c8f is the first bad commit
And to answer myself
Stefan Näwe wrote:
Stefan Näwe stefan.naewe at atlas-elektronik.com writes:
6035d6aad8ca11954c0d7821f6f3e7c047039c8f is the first bad commit
And to answer myself once more:
That's fixed in
6da8bdc fetch-pack: do not remove .git/shallow file when --depth is not
specified
Sorry for
5 matches
Mail list logo