On 2007.10.14 16:51:46 +0200, Andreas Ericsson wrote: > Björn Steinbrink wrote: >> I tried all git releases from 1.5.3 to 1.5.3.4 as well as the current >> master and all of them crashed. A small shell script to reproduce the >> problem is attached. > > Manual bisect? Ugh. This *is* the century of the competent developer > tools, you know... ;-) Then, how do I search for a good version with git bisect if I only have the one data-point "master is bad"? All I tried when testing those 5 versions was trying to find a good version so that I can actually do an automatic bisect. And I stopped at 1.5.3 because I figured that my test-case is probably just pretty uncommon and was basically always broken. Another manual "bisect" shows that 1.5.0 also crashes and as 1.4.0 doesn't even want to read my git git repository, I don't intend to go even further backwards in the history to find a good commit, unless someone tells me that it is a really good idea or how to automate finding a good commit in a sane way. Björn - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
