Here's the deal. I know you guys all think that I'm a genius and
everything, but I'm actually dumb as a board. The "design mistake"
was made so that I could have BK generate pure SCCS files and test that
I did the same thing as a known working tool, ATT SCCS. By doing that,
I easily saved myself a year of design. Making interleaved deltas work
is hard for me (we have Rick here now and he's forgotten more about this
stuff than I'll ever know, but we didn't have him when I wrote the SCCS
compat weave).
At this point, I trust our implementation of the weave more than I trust
the ATT one, and ours handles several cases that theirs doesn't, so I'm
a lot less concerned about that compatibility.
And we know that we can get better performance, and dramatically reduce
fragmentation, by sticking all the files in one big file, and we've known
this for a long time. We're gonna do it, you're gonna love, it's less
filling, it tastes great. There is only so many things that we can do at
once and this is on our short list, but it isn't at the top. Keep that
in mind as you push us to make enhancements, there is no free lunch, so
prioritize.
I'm gonna hack at least make & patch to know about the new format and
work the way they do now. So I can have your cake and eat it too.
If I can't get the FSF to take the changes, we'll just ship 'em,
we ship diff & patch already, so it's not so hard to alias make='bk make'.
----- 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/