git bisect is great for finding the revision that broke something, but there's an odd Leo specific issue to work around. For a month or more in early 2014 there are Leo commits that abort if .../.git/HEAD doesn't contain a space. It's usually "ref: refs/heads/master" but while using git bisect it's something like 8e35e492a3c1367d8441cb15b0468bfc78033580 The problem is that Leo's sniffing in the .git folder to report its version number, git recreates everything as it was "back then", *except* the content of .git.
The workaround is to export Leo for testing, something like: ... git archive HEAD | tar -x -C ~/r && python ~/r/launchLeo.py ~/r/test.leo git bisect bad git archive HEAD | tar -x -C ~/r && python ~/r/launchLeo.py ~/r/test.leo git bisect good git archive HEAD | tar -x -C ~/r && python ~/r/launchLeo.py ~/r/test.leo git bisect bad Normally this would just be python launchLeo.py ~/r/test.leo git bisect bad python launchLeo.py ~/r/test.leo git bisect good python launchLeo.py ~/r/test.leo git bisect bad but the export to a temp. dir with no .git at all avoids the problem. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
