Github now supports Subversion

We were interested in Github since parts of the project www.azati.com we began to issue under the AGPL license. On April 1 of this year, Github announced support for Subversion in read-only mode for its repositories. Until today I was sure that it was an April Fool's joke. But yesterday they announced that they had added support for Subversion also in record mode. It looks like Github is aiming at the leaders and tuned in to users who are already tired of Subversion, but have not yet matured on Git. After all, it is unlikely those who already use Github with Git will want to use Subversion. However, now many Google code fans will think about moving. The set of tools for working with Subversion does not change, you see, then you can also try Git without losing anything.

For authorization, use the standard login / password to Github (not the keys!). The paths to the Subversion repositories look like this:
svn.github.com[user]/[repository]

The code is available both through Git and Subversion with some limitations:
- there are still a couple of problems with merging when using Subversion (this is understandable);
- it is impossible to get a part of the repository as is usually possible with Subversion;
- you must have a “master” branch;
- In general, access via Subversion is considered in beta testing and there are no guarantees.

Looking forward to mercurial support from Github?