In the Cog branch of the SVN tree there is no directory for RISC OS. I could, of course, simply copy all my files and add/commit them but that seems like a bit brute force to me. I'd prefer to find out that there is a bit of SVN server command magic that will connect up the 'old' files from the plain interpreter branch.
Probably reading that damn great big SVN book would explain it eventually but if there is anyone that already knows how to do it I'd be extremely happy to know the incantation.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim In computer science, we stand on each other's feet.
Hi Tim:
On 17 Apr 2013, at 03:29, tim Rowledge tim@rowledge.org wrote:
In the Cog branch of the SVN tree there is no directory for RISC OS. I could, of course, simply copy all my files and add/commit them but that seems like a bit brute force to me. I'd prefer to find out that there is a bit of SVN server command magic that will connect up the 'old' files from the plain interpreter branch.
Probably reading that damn great big SVN book would explain it eventually but if there is anyone that already knows how to do it I'd be extremely happy to know the incantation.
`svn copy` retains file history:
http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.copy.html
Best regards Stefan
On 17-04-2013, at 12:24 AM, Stefan Marr smalltalk@stefan-marr.de wrote:
`svn copy` retains file history:
Thank you - not just the incantation but a citation for it! I've actually read the book several times but a) a long time ago and b) how often does one need to know anything more than 'co', 'up' & 'ci'?
So it looks like I need to do svn copy http://squeakvm.org/svn/squeak/trunk/platforms/RiscOS http://squeakvm.org/svn/squeak/branches/Cog/platforms/RiscOS -m "add RISC OS to Cog platforms"
I wonder if it'll be friendly?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim How many of you believe in telekinesis? Raise my hands....
On 17-04-2013, at 5:50 PM, tim Rowledge tim@rowledge.org wrote:
On 17-04-2013, at 12:24 AM, Stefan Marr smalltalk@stefan-marr.de wrote:
`svn copy` retains file history:
Thank you - not just the incantation but a citation for it! I've actually read the book several times but a) a long time ago and b) how often does one need to know anything more than 'co', 'up' & 'ci'?
So it looks like I need to do svn copy http://squeakvm.org/svn/squeak/trunk/platforms/RiscOS http://squeakvm.org/svn/squeak/branches/Cog/platforms/RiscOS -m "add RISC OS to Cog platforms"
I wonder if it'll be friendly?
Evidently not…
Ian (or perhaps Eliot?) could you please extend permissions for me to do this copy and commit to the Cog platforms/RiscOS & Cross trees?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim You can't make a program without broken egos.
On 18-04-2013, at 7:43 PM, Ian Piumarta piumarta@speakeasy.net wrote:
On Apr 18, 2013, at 10:07 , tim Rowledge wrote:
Ian (or perhaps Eliot?) could you please extend permissions for me to do this copy and commit to the Cog platforms/RiscOS & Cross trees?
Done.
Wow. It worked first time and took no time at all to execute. I was anticipating getting a message about it taking X hrs/days for queued up changes to appear - but no; whooosh! Done. When does the extension that will write all your code for you appear?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: RCM: Randomly Corrupt Microcode
It can beam you to Hawaii but you'll have to buy your program 30 days in advance.
On Apr 19, 2013, at 2:27 PM, tim Rowledge tim@rowledge.org wrote:
On 18-04-2013, at 7:43 PM, Ian Piumarta piumarta@speakeasy.net wrote:
On Apr 18, 2013, at 10:07 , tim Rowledge wrote:
Ian (or perhaps Eliot?) could you please extend permissions for me to do this copy and commit to the Cog platforms/RiscOS & Cross trees?
Done.
Wow. It worked first time and took no time at all to execute. I was anticipating getting a message about it taking X hrs/days for queued up changes to appear - but no; whooosh! Done. When does the extension that will write all your code for you appear?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: RCM: Randomly Corrupt Microcode
I thought that was a Mercurial plugin? (Git would never send you somewhere so relaxing. Maybe a pleasant desert island where you could build your own hotel out of palm leaves and coconut shells!)
frank
On 19 April 2013 22:38, Casey Ransberger casey.obrien.r@gmail.com wrote:
It can beam you to Hawaii but you'll have to buy your program 30 days in advance.
On Apr 19, 2013, at 2:27 PM, tim Rowledge tim@rowledge.org wrote:
On 18-04-2013, at 7:43 PM, Ian Piumarta piumarta@speakeasy.net wrote:
On Apr 18, 2013, at 10:07 , tim Rowledge wrote:
Ian (or perhaps Eliot?) could you please extend permissions for me to do this copy and commit to the Cog platforms/RiscOS & Cross trees?
Done.
Wow. It worked first time and took no time at all to execute. I was anticipating getting a message about it taking X hrs/days for queued up changes to appear - but no; whooosh! Done. When does the extension that will write all your code for you appear?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: RCM: Randomly Corrupt Microcode
On Fri, Apr 19, 2013 at 02:27:05PM -0700, tim Rowledge wrote:
On 18-04-2013, at 7:43 PM, Ian Piumarta piumarta@speakeasy.net wrote:
On Apr 18, 2013, at 10:07 , tim Rowledge wrote:
Ian (or perhaps Eliot?) could you please extend permissions for me to do this copy and commit to the Cog platforms/RiscOS & Cross trees?
Done.
Wow. It worked first time and took no time at all to execute. I was anticipating getting a message about it taking X hrs/days for queued up changes to appear - but no; whooosh! Done. When does the extension that will write all your code for you appear?
Be careful what you wish for ;-)
Dave
vm-dev@lists.squeakfoundation.org