Re: [RFC] Linux Kernel Subversion Howto

[Larry McVoy]

Ahh, Roman, always a joy to hear from you.

> > 			CVS		BitKeeper	% in CVS
> > 	file deltas	210,609		218,742		96%
> > 	changsets	26,603		59,220		44%
> > 
> > In other words, the CVS tree is missing no more than 4% of the deltas
> > to the source files.
> > 
> > READ THAT AGAIN, PLEASE.
> > 
> > The CVS tree has 96% of all the deltas to all your source files.  96%.  
> 
> Before you start shouting, how about you get your numbers right? Your 
> first numbers were wrong and the second numbers are still wrong:
> 
> $ find -name \*,v -a ! -path ./BitKeeper\* -a ! -name ChangeSet,v | xargs rlog | egrep '\(Logical change 1.[0-9]+\)' | wc -l
> 187576

Bzzt.  You forgot all the intial deltas which are not marked with the
logical change comment.  And just to double check my logic I tried it
with rlog (much slower but whatever):

$ /tmp/linux-2.5-cvs find linux-2.5/ -name '*,v' |
xargs rlog | grep 'total revisions' |
awk 'BEGIN { n = 0 }; { n = n + $NF };  END { print n }'
237338
$ /tmp/linux-2.5-cvs perl REVS
files=22966 revs=237338

Imagine that, the numbers match perfectly.

It's always possible I've made a mistake but you really ought to check
your work a little bit before making false claims.  It's trivial to do
what I did which is run the script over a single file and hand verify
that it is correct.  

> > My good friend Stelian would have you believe that you are missing 50%
> > of your data when in fact you are missing NONE of your data, you have 
> > ALL of your data in an almost the identical form.
> 
> [Questionable complaints that he isn't getting enough information]

First, you can get all the granularity that you want from bkbits.net.
Find the file you want, find the revision, and go backwards to the
changeset.  It takes you a few clicks to do that.  

Second, your numbers are just plain wrong.  You have 96% of the data
and anyone can validate that.

Third, as someone else pointed out you have the bk-commits list so you
have an archive of the patches and the commits.

Fourth, it is your choice to not use BitKeeper because you want to compete
with the people who are helping you.  It's not that unreasonable that
you find yourself at something of a disadvantage because of that choice.
And the disadvantage is very slight as has been shown.  You can argue
all you want about the amount of disadvantage but it is your choice that
has placed you in that position.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/