On 6/9/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
On Fri, 9 Jun 2006, Jon Smirl wrote:
> >
> > Btw, does anybody know roughly how much data a initial "cvs co" takes on
> > the mozilla repo? Git will obviously get the whole history, and that will
> > inevitably be bigger than getting a single check-out, but it's not
> > necessarily orders of magnitude bigger.
>
> 339MB for initial checkout
And I think people run :pserver: with compression by default, so we're
likely talking about half that in actual download overhead, no?
So a git clone would be about (wild handwaving, don't look at all the
assumptions) four times as expensive - assuming we only look at a poor DSL
line as the expense - as an initial CVS co, but you'd get the _whole_
history. Which may or may not make up for it. For some people it will, for
others it won't.
Could you clone the repo and delete changesets earlier than 2004? Then
I would clone the small repo and work with it. Later I decide I want
full history, can I pull from a full repository at that point and get
updated? That would need a flag to trigger it since I don't want full
history to come over if I am just getting updates from someone else's
tree that has a full history.
Of course, to make up for some of the initial costs, I suspect that some
people who are used to "cvs update" taking 15 minutes to update two files,
it would be a serious relief to see the git kind of "300 objects in five
seconds" kinds of pulls.
No more cvs diff taking four minutes to finish. I have to do that
every time I want to generate a 10 line patch. Diffs can run locally.
No more cvs update to replace files I deleted because I messed up
edits in them. And I can have local branches, yeah!
What are we going to do about the BEOS developers on Mozilla? There
are a couple more obscure OSes.
Although I guess that's one of the CVS things that SVN improved on. At
least I'd hope so ;/
Linus
--
Jon Smirl
jonsmirl@xxxxxxxxx
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html