Re: Further ArcEm development (or not)

2009-10-10 Thread Dr. David Alan Gilbert
* Peter Naulls (pe...@chocky.org) wrote: > > The ArcEm CVS has been static for quite some time. The last post to the > ArcEm mailing list is more recent, but still over a year ago. In any > case, Arculator (http://b-em.bbcmicro.com/arculator/) is probably > a superior emulator. However, what I

Re: Further ArcEm development (or not)

2009-10-08 Thread Ralph Corderoy
Hi Chris, > On Tue, 06 Oct 2009 20:26:31 -0700, Peter Naulls wrote: > > What I'll likely do then is close down the Sourceforge page. I'll > > import the ArcEm CVS into riscos.info SVN for historic value (if > > anyone really wants write access, just let me know a user > > name/password). It's p

Re: [gccsdk] Further ArcEm development (or not)

2009-10-08 Thread Ralph Corderoy
Hi Peter, > > > The ArcEm CVS has been static for quite some time. > > > > Last change 2009-09-25? > > Sorry yes. "cvs log" does things in a unhelpful order. I've been > using SVN too long. Yes, I found it annoying when I went to look. $ cvs log | > sed '/^date: /!d; s#/.. .*##; s/.

Re: Further ArcEm development (or not)

2009-10-07 Thread Chris Young
On Tue, 06 Oct 2009 20:26:31 -0700, Peter Naulls wrote: > What I'll likely do then is close down the Sourceforge page. I'll > import the ArcEm CVS into riscos.info SVN for historic value > (if anyone really wants write access, just let me know a user > name/password). It's possible I might make

Re: [gccsdk] Further ArcEm development (or not)

2009-10-07 Thread Peter Naulls
Ralph Corderoy wrote: > Hi Peter, > >> The ArcEm CVS has been static for quite some time. > > Last change 2009-09-25? Sorry yes. "cvs log" does things in a unhelpful order. I've been using SVN too long. Do you have any specific plans for ArcEm here? My biggest frustration with RPCEmu is stil

Re: Further ArcEm development (or not)

2009-10-07 Thread Tom Walker
> You destroyed RPCemu - don't now destroy ArcEm. I'm intrigued now - how did Peter destroy RPCemu? I thought it was more a combination of me quitting and the Howkins spinning off the Spoon edition that killed development in the SVN branch. Tom ---

Re: Further ArcEm development (or not)

2009-10-07 Thread Peter Howkins
On Wed, Oct 07, 2009 at 05:32:53AM -0700, Peter Naulls wrote: > If the consensus is an insistence is that it remains at SF, then > that'll be done. Still, it needs some kind of conclusion, unless > there really is on going development. I too believe that Arcem should remain on SourceForge. Whils

Re: Further ArcEm development (or not)

2009-10-07 Thread Ian Jeffray
Peter, > I still don't know if we should be linking to your page or not. > I have to assume the port has been lost (i.e, my overall fear > here) and that the link should be removed. This alone would > justify my concern. The code is checked in to SF like all the other ports. Why you should even

Re: Further ArcEm development (or not)

2009-10-07 Thread Ian Jeffray
Peter, You said: > If I > was so obviously cast in the mold for which are you > insisting for me, then I would have just moved it, no > questions asked. Should you do so, and I'm fairly sure you will, I will simply open up a new SF project to put the source back in the public domain where it bel

Re: Further ArcEm development (or not)

2009-10-07 Thread Peter Naulls
Ian Jeffray wrote: > Peter, > > You said: > > If I >> was so obviously cast in the mold for which are you >> insisting for me, then I would have just moved it, no >> questions asked. > > Should you do so, and I'm fairly sure you will, It's your prerogative to believe this, but whether I do or n

Re: Further ArcEm development (or not)

2009-10-07 Thread Peter Naulls
Ian Jeffray wrote: > Peter, > >> Please don't top-post. > > Understand common business practice and avoid the pettyness. This is a serious development discussion. Proper inline posting means the points can actually be replied to. Unfortunately your response seems to be full of insults towards

Re: Further ArcEm development (or not)

2009-10-07 Thread Ian Jeffray
Peter, > Please don't top-post. Understand common business practice and avoid the pettyness. >> I do not think it is acceptable for you to close down an opensource >> project and take it on to your private subversion server. > > riscos.info is not "private", any more than any other well-known >

Re: Further ArcEm development (or not)

2009-10-07 Thread Ian Jeffray
Peter, I do not think it is acceptable for you to close down an opensource project and take it on to your private subversion server. As a contributor, supporter and user of this project, I do not support this move. Ultimately I can see you do whatever you wish to any project anyway. Ian. Pet

Re: [gccsdk] Further ArcEm development (or not)

2009-10-07 Thread Ralph Corderoy
Hi Theo, > The only likely problem is if SF cancels the project for being > dormant. Anyone have a link to their procedure in that case? > They threatened to do that to a project I did, last update 2003, but > the website is still there (I didn't use their CVS). It requires > someone being ale

Re: Further ArcEm development (or not)

2009-10-07 Thread Peter Naulls
Ian Jeffray wrote: > Peter, Please don't top-post. > > I do not think it is acceptable for you to close down an opensource > project and take it on to your private subversion server. riscos.info is not "private", any more than any other well-known RISC OS site is. As a > contributor, suppor

Re: Further ArcEm development (or not)

2009-10-07 Thread Ralph Corderoy
Hi Peter, > The ArcEm CVS has been static for quite some time. Last change 2009-09-25? > The last post to the ArcEm mailing list is more recent, but still over > a year ago. In any case, Arculator > (http://b-em.bbcmicro.com/arculator/) is probably a superior emulator. > However, what I don't

Further ArcEm development (or not)

2009-10-06 Thread Peter Naulls
The ArcEm CVS has been static for quite some time. The last post to the ArcEm mailing list is more recent, but still over a year ago. In any case, Arculator (http://b-em.bbcmicro.com/arculator/) is probably a superior emulator. However, what I don't want to happen is for it to be lost/forgotte