Thanks Moritz! And thanks for your initiative in putting a copy on
github initially. It was our only access to the source while SF was down.
The RexxLA Board has been discussing what our plan for going forward
should be and, hopefully, there will be a decision very shortly.
As my knowledge of github is effectively non-existent, please help me
understand the process you use to do the update. Is it something like a
SVN checkout and then some sort of a "merge" on github? Is this a
manual process or is/could it be triggered by a SVN commit? And I
believe only the main ooRexx tree is currently on github, not any of the
sandboxes or other (sub)projects, correct? A better understanding of
the "mirror" process will help the Board to decide how to proceed going
forward.
Thanks once again for your efforts!
Gil B.
On 7/27/2015 4:20 AM, Moritz Hoffmann wrote:
I updated the official copy on github: https://github.com/ooRexx/ooRexx
What about a plan to escape the sourceforge chaos?
Cheers,
Moritz
On Sun, Jul 26, 2015 at 12:33 PM René Jansen <[email protected]
<mailto:[email protected]>> wrote:
As the build machine indicates, already 7 hours ago the svn was up
again.
Let’s implement our plan to get all history from it and have a
safe copy on github.
best regards,
René.
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
