Will have to leave the office, so maybe you can trigger the building of the binaries by applying the
enclosed "trigger.patch"?
* save the attached "trigger.patch" (the result of doing a "svn diff >
trigger.patch" in
"main/branches/5.0.0") to your "main/branches/5.0.0" directory
* change into the directory "main/branches/5.0.0" and apply the patch like this
svn patch trigger.patch
* this should cause three files to be changed in the 5.0.0 branch
* commit the local changes to Sourceforge:
svn ci -m "change files to trigger a new build of the release packages
with the same
revision and the latest documentation"
---rony
P.S.: You can use "svn --reverse-diff trigger.patch" to reverse the local
changes.
Index: CMakeLists.txt
===================================================================
--- CMakeLists.txt (revision 12584)
+++ CMakeLists.txt (working copy)
@@ -33,6 +33,7 @@
#/* NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
*/
#/* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
#/*
*/
+#/*
*/
#/*----------------------------------------------------------------------------*/
Index: interpreter/classes/WeakReferenceClass.hpp
===================================================================
--- interpreter/classes/WeakReferenceClass.hpp (revision 12584)
+++ interpreter/classes/WeakReferenceClass.hpp (working copy)
@@ -87,3 +87,4 @@
#endif
+
Index: interpreter/files.html
===================================================================
--- interpreter/files.html (revision 12584)
+++ interpreter/files.html (working copy)
@@ -114,7 +114,6 @@
</tr>
</table>
-
</body>
</html>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
