Hi,
On Sat, 7 Oct 2017, Ralph Corderoy wrote:
Sourceforge are mailing project admins pointing out CVS write access is
going to stop. Read access will continue, but that might be stopped too
in time. (Maintaining CVS's source is too much of a burden for them.)
Given our project-admin hats, Peter Naulls or I can convert the CVS to
Subversion or Git following SF's instructions.
https://sourceforge.net/p/forge/documentation/CVS/
Subversion doesn't take much effort though the resulting repo might have
problems that aren't initially spotted, e.g. character-encodings in
comments. Probably nothing that can't be sorted out later. I'd be
willing to do that.
Git probably takes a bit more time, that I don't have right now but
might soon. Can those that have recent CVS commits, Ian?, state a
preference for Subversion or Git. Does RISC OS support both Subversion
and Git now?
Either option is fine with me. RISC OS doesn't have a Git client yet, but
there is a Subversion client (however I haven't had reason to use it in
years, so I'm not sure how well it runs on the latest hardware/OS
versions)
Lack of native source control clients isn't really a problem for me since
I tend to do most source control via a Linux PC.
Cheers,
- Jeffrey
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--
arcem-devel mailing list
arcem-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/arcem-devel
