|| ||Chia-liang Kao <firstname.lastname@example.org>|
|| ||[ANNOUNCE] Subversion/svk mirror of the linux tree|
|| ||Sat, 21 Aug 2004 12:05:46 +0100|
I'm pleased to announce a Subversion/svk mirror of the linux kernel
Web interface at http://svn.clkao.org/svnweb/linux/log/cvs/
Meanwhile svk 0.19 is available: http://freshmeat.net/releases/170508/
Before you start flaming about Subversion being centralized and not
the right model for kernel development, please take a moment to read
up about the additional features svk offers.
Please keep me CC'ed for comments, as I'm not subscribed to the list.
* I heard that Subversion isn't the preferred revision control system for
Linux. Why do you want to provide this mirror?
I am not telling anyone to switch to Subversion for linux development,
just helping to make the linux kernel more easily accessible to
everyone. Users who want to checkout the latest version of the kernel
can use the increasingly popular open-source svn client to checkout.
Developers can now use svk to mirror the above url, create a local and
offline branch, generate diffs against the trunk and easily submit
their patches upstream.
You can learn more about svk at http://svk.elixus.org/.
Since the tree is quite large, you might not want to grab the entire
repository's history. You can start off with the 100 most recent
revisions like this:
svk mirror //linux/trunk svn://svn.clkao.org/linux/cvs
svk sync --skipto HEAD-100 //linux/trunk
* svk is built on-top of Subversion? I heard Subversion is slow.
Doesn't that means svk is even slower?
svk only uses the lowest two layers of Subversion, which is
well-maintained and constantly improving. On large trees that reside
locally, svk checkout is about twice as fast as svn.
* How is the mirror provided?
svk can also mirror non-subversion repositories with the nice and
extensible VCP framework.
The exported cvs tree is rsynced, and then:
svk mirror /linux/cvs cvsbk:/home/cvs/linux:linux-2.5/... --branch-only=trunk
svk sync /linux/cvs
The cvsbk VCP source driver can also be found on CPAN.
The first mirror took quite a few hours for the 20000+ changesets, and
the memory usage is around 200M. Subsequent runs are usually done
within 5 minute.
Special thanks to xs4all.nl for providing hardware and bandwidth for
svk development and such mirror service.