On Mon, Jul 26, 2010 at 8:27 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: > 04:23 * mcgrof is confused, I just did a git bisect -i on > wireless-testing on some patch on Fri Jul 2 00:09:49 2010 and ended > up with a 2.6.34 top level > Makefile > 04:23 < mcgrof> it was git rebase -i ba17bc5e55ba541d2a8765fca53b6883b667ab21 > 04:23 < mcgrof> eh > 04:24 < mcgrof> how am I supposed to bisect wl now > 04:24 < mcgrof> the odd thing though is that the top commit is ancient > 04:24 < mcgrof> http://paste.pocoo.org/show/242077/ > 04:24 < mcgrof> but the other ones are OK > > I realize we should use wireless-2.6.git to bisect stable but I need > to bisect against recent patches that spans different master- tags > from you, I figured git bisecting wireless-testing would work now that > you are using a different method to move your tree forward but am I > wrong? Should I only bisect between master tags still? Heh I just realize what I said didn't make sense, what I meant was I was *going* to bisect but in order to first find my first good starting point I am going through the tree trying to find a good starting point to bisect and to do that I use interactive rebase (git rebase -i sha1sum) to specific sha1sums until I find a good compile that works. Only after I've done this would I then bisect. The interactive bisect on ba17bc5e55ba541d2a8765fca53b6883b667ab21 throws me back to 2.6.34 though, for some odd reason. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
