« Google DNS | Main | Moving (back) to the Finder »



Great news! Thanks for adding a useful feature to a rock-solid, and exceptionally well managed, service.


And Mercurial? ;-)


I use an ssh config file, with which it appears that there is no need to use absolute paths, making the git remote entry simpler.

My ~/.ssh/config includes (server and username changed):

Host rsync.net
Hostname usw-s003.rsync.net
User 12345

Now all I have to do is:
ssh rsync.net git init --bare test.git
git clone rsync.net:test.git


Really excellent, thank you. Being able to 'git init' on the server is a whole lot easier than locally creating and scp'ing a bare repo before I can clone. GitHub is great for public stuff, but git+rsync.net just became my first choice for stuff I really can't afford to lose.

John Kozubik

@uou : No plans for mercurial, or any other DVCS support in the future. Please see the paragraph above:

That being said, we will not be adding any further such systems. There will not be cvs or Mercurial support in the future (although I am aware of some ways to run Mercurial over a git, or subversion "transport" and users are free to do so).

Once we add mercurial there is going to be another DVCS de jour, and so on. I feel like things have solidified a bit with svn and git as the "standard" offerings and we don't want to add any more binaries and libraries to these systems.

I'd appreciate hearing any comments on our interpretation of the landscape ... is hg supplanting svn and git en masse ?


The more standard tool to use when you just need something to return "true" is /bin/true. Any reason not to use that instead of /bin/echo?

Regarding hg, I would guess that it is more likely to supplant svn and maybe cvs than git.


Yay, thank-you! :D


I would say Mercurial is worth considering. I say this because it has been around just as long as git has (they both started at the same time) and due to its easier migration path, a lot of subversion users are migrating over to Mercurial rather than git.

One should also consider the fact that there are far more cross-platform third party extensions and apps available for Mercurial than there are for git.

I think the above points together with Mercurial's excellent documentation and the fact that Mozilla, Sun and Python all use it as their DVCS would suggest to me at least that it is not a DVCS de jour and will be around for the long haul (likely to the detriment of Subversion).

John Kozubik

@Wodin : You are correct regarding the 'true' command. The explanation is, we need 'echo' in the chroot jail for other rsync.net functions, and do not need 'true', so it's a very small optimization towards keeping the chroot jail as small and simple as possible. In this case, probably superfluous, since 'true' is so simple.

@ gpenguin : Your points are well taken. There is one other issue, though ... if we can implement mercurial in a manner that is similar to how we implemented svn and git, using only components written in C, then we can consider it. But we cannot put a python interpreter, etc., into the chroot jail.

How much / what portions of hg are in python ?

Paul Bx

Very cool additions to the service, thanks!

Though I respect your desire to keep things simple, I'm another user who'd be happy to see Mercurial support. Q.v. above arguments.

The "DVCS de jour" problem you fear is no longer relevant IMO -- it's very 2007. Sure, there's a chance that after you add hg somebody will pop up and ask for bzr or darcs -- but they really are outliers at this point. And CVS is a legacy system with well-known migration paths. It's all about Git and Mercurial now.


@John Kozubik: I hadn't appreciated the python complication... I believe hg is entirely python based which I guess will rule it out unfortunately. A shame because I love it.

Yves Junqueira

This is great, great news. Thank you for adding git support.

Kirill Miazine

There's a way to have better and cleaner URLs.

Look (my userid replaced with 1234):

    > svn info svn+ssh://[email protected]/repos
    Path: repos
    URL: svn+ssh://[email protected]/repos
    Repository Root: svn+ssh://[email protected]/repos
    Repository UUID: 3a853746-78c0-dc11-86f3-0211d8aafdce
    Revision: 4
    Node Kind: directory
    Last Changed Author: km
    Last Changed Rev: 4
    Last Changed Date: 2008-01-11 21:13:46 +0100 (Fri, 11 Jan 2008)

Neat, no? The real repository root is still /data2/home/1234/repos

I created a new ssh key for svn and added following to my ssh config file:

  Host svn.krot.org
    Hostname ch-s010.rsync.net
    User 1234
    IdentityFile ~/.ssh/id_dsa_svn

Then I appended the new public key to 10311's authorized keys, but with a special command option prepended:

    command="/opt/subversion/bin/svnserve -t -r /data2/home/1234" ssh-dss AAAAB3NzaC1kc3MAAACBAKFn6AFsqy9XKQzrwsckhm9KsDWDKxDNVmGF6jME......

Now short path can be used to address the repositories and in case you move the directory somewhere that will only require one single change in the authorized_keys file.

The comments to this entry are closed.