forwarded 611946
http://thread.gmane.org/gmane.linux.kernel.wireless.general/65397
reassign 611946 linux-2.6
tags 611946 + upstream
found 611946 linux-2.6/2.6.37-1~experimental.1
found 611946 linux-2.6/2.6.37-1
# bisected to v2.6.35-rc1~473^2~167^2~346
found 611946 linux-2.6/2.6.35~rc4-1~experimental.1
quit
Tony Houghton wrote:
> I think I
> successfully found the "bad commit" with git bisect so I've cross-posted
> the result to this bug and linux-wireless.
Thanks!
> I was a bit puzzled by git
> bisect though because it seemed to be getting versions/tags out of
> order. For example, I found a commit after tag 2.6.34 to be "good", but
> eventually I homed in on 2.6.33. Is that normal, perhaps because they
> originated from different branches which were merged apparently out of
> order?
Exactly, it's from nonlinear history. See
https://git.wiki.kernel.org/index.php/GitFaq#Why_does_.22git_bisect.22_make_me_test_versions_outside_the_.22good-bad.22_range.3F
and
http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110224195143.GA17412@elie
