> (For current svn users I assume using svn would become effectively > impossible; the only tool I could find to do this is server-side and > essentially maintains git and svn repositories in parallel.)
FYI, any Git repository on GitHub also functions as a Subversion repository: $ svn checkout https://github.com/WebKit/webkit/trunk WebKit A WebKit/.dir-locals.el A WebKit/.gitattributes A WebKit/.gitignore A WebKit/.qmake.conf A WebKit/CMakeLists.txt A WebKit/ChangeLog A WebKit/ChangeLog-2012-05-22 A WebKit/Examples A WebKit/Examples/ChangeLog A WebKit/Examples/NetscapeCocoaPlugin A WebKit/Examples/NetscapeCocoaPlugin/English.lproj A WebKit/Examples/NetscapeCocoaPlugin/English.lproj/InfoPlist.strings A WebKit/Examples/NetscapeCocoaPlugin/Info.plist A WebKit/Examples/NetscapeCocoaPlugin/MenuHandler.h A WebKit/Examples/NetscapeCocoaPlugin/MenuHandler.m … You can even use Subversion branches to create pull requests on GitHub (though I don't know what the performance would be like for a repository as large as WebKit): <https://github.com/blog/1178-collaborating-on-github-with-subversion>. GitHub doesn't currently make the Subversion<->Git bridge available for non-GitHub repositories. I don't say this to try to convince anyone to switch to Git or GitHub; I just thought it seemed relevant. -Adam _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
