The only reason that I’ve used the subversion support in the past five years has been a horrible hack using git-svn to clone part of a GitHub repo as a submodule. I wish git had a way of integrating filter-branch and submodule so that this could be supported natively.
I guess they can release the https://svnhub.com/ domain then. While I haven’t used Subversion for probably a decade, I’m still forced to use a “subversion-like” system (Team Foundation Services) for some legacy work code.
The impressive thing was that they supported subversion as a client for the same repositories git, rather than supporting subversion hosting as a separate offering. This meant that you could create a repo, work with svn, and then decide to move to git without any data migration and even work with other people who stayed with svn.
The only reason that I’ve used the subversion support in the past five years has been a horrible hack using git-svn to clone part of a GitHub repo as a submodule. I wish git had a way of integrating filter-branch and submodule so that this could be supported natively.
Everything needs to be a monorepo. You are no longer permitted to partially check out a repository. /s
I guess they can release the https://svnhub.com/ domain then. While I haven’t used Subversion for probably a decade, I’m still forced to use a “subversion-like” system (Team Foundation Services) for some legacy work code.
TIL Github supported Subversion.
It was originally announced as an April Fools’ joke, but it actually worked.
The impressive thing was that they supported subversion as a client for the same repositories git, rather than supporting subversion hosting as a separate offering. This meant that you could create a repo, work with svn, and then decide to move to git without any data migration and even work with other people who stayed with svn.
Wow, that is neat!