Yeah, I think BK can do this, most of what you are describing is covered
by already existing BK commands and practices. There are literally dozens
of different sites using BK to track the kernel and both internal and
external sources of patches. I'm sure there are issues that need to be
resolved and we'll try to do so.
I might be mistaken, I also get the feeling that your real issue might
be that you don't like/understand/something BK and you are pushing for a
different answer. That's cool, there are now two patchbot projects you
can go join and start coding. Some of our biggest fans are people who
have tried that and discovered exactly how complex the problem space
really is, so it's actually in my best interest to encourage you to
go help out with one of those projects. If you solve the problem, the
kernel benefits and I get to learn something: that's good. Or you don't
and you'll come to respect BK: that's good too, at least I like it.
So have some fun, this is actually a more challenging area than any
kernel work I've ever done or seen, including SMP threading, so the more
you get into it, the more fun you can have (assuming that banging your
brain against some hard problems meets your fun definition).
----- 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/