Ben Collins wrote:
> What part of the structure of the BK repo don't you understand? Didn'y
> you pay attention to what Larry said? The tree looks like branches that
> always return to the trunk. To put this into CVS, he had to choose a
> line of those branches that contained the _most_ changesets (which
> doesn't always equate to the most important, or largest deltas). There
> are some changesets on the side that are not included here. Are all of
> those changesets empty merges? No.
What are you attempting to insinuate?
I think BK had has positive benefits to all Linux kernel hackers,
whether or not they use BitKeeper. The current patch flow is pretty
amazing, and we seemed to have avoided the Linus burn-out that
threatened to come to pass pre-BK.
It's getting to the point where it seems like every time BitMover does
something to appease the non-BK crowd, people (a) read evil intentions
into the action, and/or (b) just keep asking for more.
Can someone please tell what is the overall point? what is the endgame
here? what is a concrete technical solution that will satisfy you
(Ben), Pavel, and everybody else?
Jeff
-
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 : Sat Mar 15 2003 - 22:00:32 EST