You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand the question correctly, you want to continue using the `svn`
protocol and not migrate your project to GitHub (which would require you to
switch to Git), correct?
If so, consider moving your project to SourceForge. SourceForge supports svn
natively, as well as offers an easy import service for your Google Code project.
See:
https://code.google.com/p/support-tools/wiki/MigratingToSourceForge
Original comment by chrsm...@google.com on 16 Mar 2015 at 4:19
Yes, that's half correct, but I'd rather not go (back) to Sourceforge, we'd
like to host the SVN ourselves on our own server.
For instance, when we moved from Sourceforge to Google Code, we were able to
download a large zip/tgz file of the actual repo (the one with the svn control
folders like conf, dav, db, format, hooks, locks in the root, instead of what
you get from a checkout--content like 'trunk').
We've already moved the main project to Github, we were just hoping to keep the
old SVN for people to be able to grab older releases (or anything that didn't
transfer properly to Github).
I hope that I'm just missing an option that's already available in the current
interface, but thanks for any help.
Original comment by f...@processing.org on 17 Mar 2015 at 12:49
Original issue reported on code.google.com by
f...@processing.org
on 16 Mar 2015 at 4:15The text was updated successfully, but these errors were encountered: