björn wrote: > If it is that consistent then it would be great if somebody could do a > bisection with Git to find the exact commit where it happened. I had > a look at the commits between 40 and 41 but I can't "guess" which one > might be the offending commit. Does anybody with this problem know > how to do this and have time? (I still can't reproduce reliably but > it has happened once or twice.) >
It looks like this is the culprit: 662aa32b399c1149daa1cd3a2b5bccc8e75f589a is first bad commit commit 662aa32b399c1149daa1cd3a2b5bccc8e75f589a Author: Bjorn Winckler <[email protected]> Date: Wed Jan 7 20:19:44 2009 +0100 Prune unnecessary code, clarify comment :040000 040000 0e451b9611fb96374a76c4319e86aa0d56fdc19e d36cd9b7ad35c238218df462a9233614e4a0d480 M src 662aa32b399c1149daa1cd3a2b5bccc8e75f589a --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
