From: Achim S. <lmm...@ma...> - 2010-03-21 23:50:57
|
Hi Toby, >> With git bisect, I was able to track it down to commit >> 37ccbb4b50dc0c10f431c931a8e9842ca6152d96 which represents a merge of >> the fx-mixer-rework branch. > Lot's of things have changed in this branch. Maybe you can bi-sect > within the fx-mixer-rework branch? > git checkout -b fx-mixer-rework origin/fx-mixer-rework Done that. Some of the commits happily crashed the system on startup, so I skipped them. Here's the result: ---------------------------------------------------------------------- There are only 'skip'ped commit left to test. The first bad commit could be any of: f6f4414c989e55a867045a2575252b8b78289942 95eb60f05fc2dc190e8c8e84ffcbcbba7fad8e7c We cannot bisect more! ---------------------------------------------------------------------- The last known good commit was 3fa96a576c621a2ac9f470c557ec3f5e2f80df16. bye, Settel |