By the way, if you look at Documentation/BUG-HUNTING which describes how
to do binary search to track down bugs, you'll notice you can now do the
same thing with BK at a much finer granularity. It's possible to track
down bugs to the changeset which caused the bug, rather than the release.
Which is what Paul is talking about, but he's talking about doing it over
a small set of csets. You can do it over a large set of csets as well.
File this away as a thing you can do and if you ever need the details,
contact me and I'll walk you through it if it isn't obvious.
----- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Next message: Greg Banks: "Re: [kbuild-devel] Re: 64bit clean drivers was Re: Linux 2.4.20-pre1"
- Previous message: Paul Larson: "Re: Announce: daily 2.5 BK snapshots"
- In reply to: Paul Larson: "Re: Announce: daily 2.5 BK snapshots"
- Next in thread: Martin J. Bligh: "Re: Announce: daily 2.5 BK snapshots"