No. Try:
"You're whining, here's how fix it, because I don't have time or
motivation"
Larry went to a lot of trouble to listen to what kernel developers
wanted, and a lot of work to implement some of it. I expect same courtesy
of everyone who is complaining.
I am not expecting any 'enhancements to bitkeeper'.. that is Larry's job.
> If additional development around bitkeeper is needed then the onus
> is upon the bitkeeper side to do that work. (And yes, there are
> sides now).
If Larry can make good on his 'threat' to write a read-only cvs pserver
interface to BK, I think he's done his part. (BK -> $OTHER_SCM)
Then I'd really like to see scripts to make it easy to go from
$YOUR_FAVORITE_SCM -> patch -> BK, while keeping important metadata, like,
oh, say, comments. The patch->BK part is already done. It's up to the
other 'side' now to get changes from $YOUR_FAVORITE_SCM into BK without
either losing lots of information, or taking lots of time.
Various people have probably already done all of this. Now can someone
bother to spend some time to find the best methods for this and integrate
it into a nice 'packaged' setup? (along with a 'HOWTO')
-- 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/