Silly BK statistics

[Larry McVoy]

You guys work way too hard.  The BK openlogging tree, which has all
changesets ever made by anyone in the Linux kernel, was getting big.
Really big.  The nodes in the graph have internal "serial numbers"
which are currently 16 bits, i.e., there can't be more than 64K nodes
in the graph.

I sent mail to some of my engineers this morning saying "hey, I suspect
the Linux openlogging tree is about overflow, we need to go to 32 bit
ser_t's."  I had no idea how close we were, I just knew it was a problem
we needed to solve.

I just got mail from one of the team which reads: "With 199 serials shy
of overflowing , the 32 bit version is now installed".

What that means is that in about a year, you've managed to create 65,337
changesets.  That's 179 per day, 7.4/hour, 24x7.  You guys are busy.

To put that in perspective, the most active project on sourceforge today,
Gaim, has 805 commits to its changelog.  Over 3.5 years.  That means you
are changing your source base 284x more often than they are.  And that's 
just the BK users, that doesn't count the people not using BK, which are
a substantial fraction.

No matter how you slice it, it is pretty amazing rate of change.
If change is good, you guys rock, I've never seen anything like it.
-- 
---
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/