Linux survived in the past without much history, and if a replacement arrives, people can make the switch even with a degraded history. In very little time that switchover would seem as remote as the pre-BK times are now.
Right now I don't see why its necessary to track the Linux repo in 100% detail for SCM development; There are plenty of other big trees to test on if you need every detail. Time spent tracking Linux are probably better spent improving an alternative SCM, most of which have plenty of wishlist items awaiting developers. For kernel development, yes it's painful for SCM developers or purists, but you can still work just fine with patches. Maintainers certainly benefit from BK, but for developers on the leaves of the hierarchy there's not that much difference.
- Jim Bruce - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
