Re: Documentation error regarding peek4s and peek4u functions
- Posted by jaygade Sep 10, 2009
- 1206 views
Should it be to trunk? Did I mess up?
<snip>
Sorry about that.
Yeah, the trunk is where main development happens. In general, tags are meant to be static.
You didn't mess anything up, don't worry about it. It was brought up, however, as the tag 4.0b2 is pretty much static, or dead. i.e. it stops there and will never be used again. It's the end of the branch. No code will ever continue on from there. So, your changes committed will never be distributed to anyone else. That's the main problem.
You might have something like this:
r123 -> r124 -> r125 -> r126 -> r127 -> r128 -> r129 -> trunk
\- tag 4.0b2 (r124) \- tag 4.0b3 (r128)
So, those tags are never put back into the mainline trunk, which will eventually become 4.0b3, 4.0rc1 and finally 4.0 final. You need to do:
svn co https://rapideuphoria.svn.sourceforge.net/svnroot/rapideuphoria/trunk
and then work from the trunk directory. You'll need to make your changes again in trunk. However, take note that I changed the file extension from .exu to .ex, as we no longer recommend using .exu for Unix only scripts. They are all .ex, as they are all run with eui.
Jeremy
Okay, got it. I read all this stuff several months (or a year or two??) ago but I've forgotten it all.
Also, WRT exu vs. ex, I got that. But I noticed that it was set to exu in beta2 which is why I went with that convention. I'll keep that in mind as I go through the rest of it. It looked to me like someone had changed it from ex to exu in the past.
