https://bugs.freedesktop.org/show_bug.cgi?id=27402
--- Comment #4 from Chris Rankin <ranki...@googlemail.com> 2010-04-03 03:46:37 PDT --- (In reply to comment #3) > Read > http://www.mail-archive.com/mesa3d-...@lists.sourceforge.net/msg12767.html > for more explanation. Yada yada yada! The big problem with "git bisect" is that (despite what some people seem to think), it is NOT a tool which you can ask an inexperienced person to turn a handle blindly and have an answer pop out of a slot. There is no guarantee whatsoever that an intermediate build will either compile or work. In fact, it is becoming increasingly clear that I have no friggin' clue how "git bisect" is actually working because I have tried to bisect again this morning! Between now and last night, someone has checked something in that has FIXED this problem. So lets see: This is the most recent commit in my local tree: commit f618867645b3ce2570958bfacc1faf8c88e7a620 Author: Brian Paul <bri...@vmware.com> Date: Fri Apr 2 22:38:18 2010 -0600 mesa: display list support for GL_EXT_transform_feedback $ git bisect start $ git bisect good And the last commit I remember seeing last night (when it was still broken) was this one: commit f6c7b911653fb1508256c63518ef0bd15d68186e Author: Dave Airlie <airl...@redhat.com> Date: Sat Apr 3 07:00:03 2010 +1000 r300g: make dithering work like fglrx. From fglrx traces the dithering is never enabled. So lets declare that one as "bad": $ git bisect bad f6c7b911653fb1508256c63518ef0bd15d68186e Some good revs are not ancestor of the bad rev. git bisect cannot work properly in this case. Maybe you mistake good and bad revs? ?????? WTF ??????? How can a commit that I already had last night be more recent (in the sense of when I added it into my local tree - which is the only measure that matters) than one I only picked up a few minutes ago this morning? So **NO**, I am not going to use "git friggin' bisect" for you! -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
