-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The subversion repository (including trunk, tags, branches) takes up 27MB.
A working copy checked out from Subversion (just trunk) occupies about 12MB; about 5.1MB are the working files, about 6.2MB are .svn/ directories and their contents (that should add up to ~11MB by my count, but anyway...). A Mercurial repository clone (which includes all trunk history information, plus the working copy), occupies 13MB. Again, 5.1MB of this is the working copy's files; a clone of the repository without a working copy ocupies 7.9MB. I don't know how the Subversion repository should compare to the Mercurial repository; the Mercurial repository is the trunk only, whereas the Subversion repository also has history for four release branches, 16 bug branches, and reference tags for all of these. However, tags are very, very cheap, and the additional information represented in the branches are probably not terribly large, so it's difficult to compare the "everything" Subversion repository to the "trunk-only" Mercurial repository: it could be very impressive that Subversion holds all that stuff in only 19MB more than the Mercurial repo, or it could be that even a trunk-only Subversion repository would not be a whole lot smaller than that 27MB. However, the fact that the entire Mercurial repository compares approximately equal to a Subversion working copy's metadata cruft is pretty impressive. Of course, a large part of this is probably due to the fact that Subversion's "cruft" includes pristine copies of all files from the last checkout, so that a simple "svn diff" doesn't have to involve network traffic. Since a Mercurial repository includes the entire histories, it doesn't need to do this. :) Note that this doesn't say anything about how Mercurial or Subversion compare to other DRCSses; and, of course, efficient storage is far from one of the most significant considerations for choosing an SCM, in comparison with other things. Still, if you're wondering if allocating space for an entire repository is going to be problematic in comparison to storing just a working copy: worry not! :) ...of course, if using Mercurial to work with Wget is the only reason you have to have Python installed on your system, well, that's another thing... :D - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8b1l7M8hyUobTrERCCRYAJ4kYswo2lGAhpkkNgCIUOnNG5SIOgCeJcgj 4Hfk7DKe7R8EZOhG9imV+jo= =LGHf -----END PGP SIGNATURE-----
