RE: Sourceforge Ditching CVS Write Access.
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: >> 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 512 KiB RAM, > maybe the minimum system requirement will need to be 1 MiB RAM. > > He will send you a floppy disc once it is ready. Or for a slightly more serious answer - the current port of SimpleGit should work down to RISC OS 3.5 (i.e. standard GCC/UnixLib compatibility claims). I'd expect the amount of RAM you have to be the main blocker to using it on older machines (it'll have come from a world of memory-mapped files and virtual memory, so large commits or large repositories are likely to eat up lots of RAM). Cheers, - Jeffrey -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
Re: Sourceforge Ditching CVS Write Access.
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 Arthur. Not yet sure if it fits in 512 KiB RAM, maybe the minimum system requirement will need to be 1 MiB RAM. He will send you a floppy disc once it is ready. Or for a slightly more serious answer - the current port of SimpleGit should work down to RISC OS 3.5 (i.e. standard GCC/UnixLib compatibility claims). I'd expect the amount of RAM you have to be the main blocker to using it on older machines (it'll have come from a world of memory-mapped files and virtual memory, so large commits or large repositories are likely to eat up lots of RAM). Cheers, - Jeffrey -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
Re: Sourceforge Ditching CVS Write Access.
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 512 KiB RAM, maybe the minimum system requirement will need to be 1 MiB RAM. He will send you a floppy disc once it is ready. Have fun Steffen aka hubersn -- Steffen Huber LambdaComm System – Welcome to Trollinger Country stef...@huber-net.de Private homepage http://www.huber-net.de/ RISC OS Blog http://riscosblog.huber-net.de/ -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
RE: Sourceforge Ditching CVS Write Access.
Wow, this email's a reply from a while back. I don't think I ever saw the original, sorry. I'd vote for git, especially if that's coming to RISC OS (26bit?) Ian -Original Message- From: Jeffrey Lee Sent: 16 November 2018 00:39 To: arcem-devel@lists.sourceforge.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/ Any updates on this? It looks like we might be missing out on some new contributions (and at some point, I'd certainly like to do some more work as well). https://www.riscosopen.org/forum/forums/11/topics/12740 > 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? Previously I said that either option is fine with me, but I think I'm leaning more towards git now. RISC OS should have a functioning git client "soon" (and a subversion client has been available for a number of years). Cheers, - Jeffrey -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
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/ Any updates on this? It looks like we might be missing out on some new contributions (and at some point, I'd certainly like to do some more work as well). https://www.riscosopen.org/forum/forums/11/topics/12740 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? Previously I said that either option is fine with me, but I think I'm leaning more towards git now. RISC OS should have a functioning git client "soon" (and a subversion client has been available for a number of years). Cheers, - Jeffrey -- arcem-devel mailing list arcem-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/arcem-devel
Re: Sourceforge Ditching CVS Write Access.
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
