As I’ve blogged before, the mirrors update in response to the svn-commits mailing list. This means that we don’t have to hammer 520 GNOME modules on a hourly basis. It also means we are nearly always up to date. I’ve tweaked the script that manages this:
- Previously, the script would only do updates of existing modules. But now it will automatically mirror new modules the first time something hits the commits list for them, for both Bazaar and Git
- For git, a new clone is created. It is repacked. Various config settings and symbolic references and internals are poked.
- For bzr, we just need to run bzr svn-import. Its not needed, but I also create a full text search index of trunk for later secret fun.
- Updates are now batched. Example: If 3 e-mails arrive together for tracker, that means that svn.gnome.org gets poked 3 times more than needed. So I batch updates together. Faster, cheaper, saner.
You git speed freaks will be pleased to know you can now clone over git://.
cd ~
git clone git://git-mirror.gnome.org/git/conduit
cd conduit
git svn init -s svn+ssh://svn.gnome.org/svn/conduit --prefix=origin/svn/
git svn rebase
Hope you enjoy the extra speed ;-
Pretty neat stuff. What i don’t understand is why we still need to deal with git-svn if you have provided us with a git repo?
You need to use git-svn if you want to commit to SVN from your local git repo. If you don’t plan to commit, then you can forget about git-svn.
Is there any plan to have a Mercurial’s one?
[...] svn repozitorija u svom omiljenmo dvcsu tako da se već danas možete igrati sa GNOME Bazaar i GIT GNOME [...]