http://bugzilla.kernel.org/show_bug.cgi?id=7706
------- Comment #40 from [EMAIL PROTECTED] 2007-08-14 09:19 ------- got it - continue bisecting... greets [EMAIL PROTECTED] schrieb: > http://bugzilla.kernel.org/show_bug.cgi?id=7706 > > > > > > ------- Comment #39 from [EMAIL PROTECTED] 2007-08-13 18:18 ------- > Aha, ok you hit the nasty one, which is talked about here > http://www.kernel.org/pub/software/scm/git/docs/v1.0.13/howto/isolate-bugs-with-bisect.txt > Towards the end, read: > It really works wonderfully well, except for the case where there was > _another_ commit that broke something in between, like introduced some > stupid compile error. In that case you should not mark that commit good or > bad: you should try to find another commit close-by, and do a "git reset > --hard <newcommit>" to try out _that_ commit instead, and then test that > instead (and mark it good or bad). > > You can do "git bisect visualize" while you do all this to see what's > going on by starting up gitk on the bisection range. > > How about that? git-reset --hard <some close commit here>, then git bisect > visualize - and see what happens... > > > -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
