T
Tom Copeland
Hello all -
For folks who are still using RubyForge's svn support - we're looking =
into switching it over to using svn+https (vs the current svn+ssh) for =
commits. I don't think this will cause anyone any issues - should be as =
simple as an "svn switch" for folks who have a checkout of an existing =
repository.
Does anyone have any objections to this? Just wanted to make sure there =
wasn't some potential issue I hadn't thought of...
Thanks,
Tom
For folks who are still using RubyForge's svn support - we're looking =
into switching it over to using svn+https (vs the current svn+ssh) for =
commits. I don't think this will cause anyone any issues - should be as =
simple as an "svn switch" for folks who have a checkout of an existing =
repository.
Does anyone have any objections to this? Just wanted to make sure there =
wasn't some potential issue I hadn't thought of...
Thanks,
Tom