Then we move on to another system. This is why I think we need some kind
of gateway to another SCM. If BK goes away, we could export everything to
tarballs and patches or whatever, but it would be a large PITA, and stop
lots of people's development for awhile. (I've done bk->cvs this way once
before, it was really ugly, and I never want to do it again given the
choice).
I'd really like everyone that's bitching about BK to shut the hell up and
go work on some scripts to allow a maintainer to easily manage a
BK<->$OTHER_SCM gateway. Either give me a working alternative to BK or go
run for political office. Until I see an alternative, I'm going to
continue advocating for real developers to use BK, and complainers to show
me an alternative.
-- Troy Benjegerdes | master of mispeeling | 'da hozer' | hozer@drgw.net -----"If this message isn't misspelled, I didn't write it" -- Me ----- "Why do musicians compose symphonies and poets write poems? They do it because life wouldn't have any meaning for them if they didn't. That's why I draw cartoons. It's my life." -- Charles Schulz - 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/