So long as it'll work on a 256MB RiscPC with Adjust, I'm happy ;)
I.
-Original Message-
From: Jeffrey Lee
Sent: 16 November 2018 18:47
To: arcem-devel@lists.sourceforge.net
Subject: Re: Sourceforge Ditching CVS Write Access.
On Fri, 16 Nov 2018, Steffen Huber wrote:
>
On Fri, 16 Nov 2018, Steffen Huber wrote:
Ian Jeffray wrote:
I'd vote for git, especially if that's coming to RISC OS (26bit?)
I expect Jeffrey is currently (after successfully initiating the
port of SimpleGit) working on a Git client for all Acorn machines
starting with the A305 running Art
Hi Ian,
> Ian Jeffray wrote:
>
> I'd vote for git, especially if that's coming to RISC OS (26bit?)
I expect Jeffrey is currently (after successfully initiating the
port of SimpleGit) working on a Git client for all Acorn machines
starting with the A305 running Arthur. Not yet sure if it fits
in
orge.net
Subject: Re: Sourceforge Ditching CVS Write Access.
Hi Ralph,
On Sat, 7 Oct 2017, Ralph Corderoy wrote:
> 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/
Hi Ralph,
On Sat, 7 Oct 2017, Ralph Corderoy wrote:
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/
Any updates on this? It looks like we might be missing out on some
new
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, Pe
Hi,
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
Subver