> Personally, I'd love to see the *changes* in what passed and failed
> posted every day - the whole result set is obviously too big. The
> quicker people know what's wrong, the quicker it gets fixed, before
> we build more on top of an unstable foundation.
I really like "fix it before we build on an unstable foundation".
It seems to me that we could get to something like tinderbox (? One of the
mozilla tools). What I'm imagining is something like a web page which
has a set of links in which point at the csets which cause the problem.
In order to make this work, we need to fix BK/Web to talk URLs with
"keys" instead of revs because, as some of you have noticed, revs change
when there is parallel development which makes the URLs pretty useless
if they contain revs.
If you need that fix in order to be able to have a list of URLs pointing
int BK/Web on bkbits.net, bug me about it, we'll do it right away.
I like the idea of having a status page which says "these changesets
cause problems". You can have two links, one which gets you to the BK
cset html and the other which gets the patch corresponding to the cset.
-- --- 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/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:19 EST