Hi Jon,
Since I am not a native speaker I did not want to do the commits as I assume
they need some checking linguistically. I am not sure if this help, but for
myself I have decided to download the entire SVN tree, like this
svn checkout --username=perolovjonsson
svn+ssh://perolovjons...@svn.
Would it be easier to have commit rights on the documentation repo for all
developers who have them on the code repo?
Would it be better to have the docs source in the same repo as the code ... to
be in sync with releases?
best regards,
René.
> On 23 Oct 2025, at 17:18, Sahananda wrote:
>
>
I'm not having a great deal of success here.
I have checked out svn://svn.code.sf.net/p/oorexx/code-0/docs to
c:\ooRexxSVNDocs\ on my Windows laptop
Within that folder I can see the tree that matches what is in the top of
the patch
Following my instructions from TortoiseSVN 1.7 Beginners guide (ad
Dear P.O.,
thank you for looking into this!
On 23.10.2025 14:56, Sahananda wrote:
It's a while since I used the SVN, but I just updated my working copy.
I've never applied a patch, but I thought I would give it a try.
My manual says
Open the patch and look at the first line to determine where
It seems that you are looking at main/trunk, I think that docs are located
at
docs/trunk, there you'll find docs/trunk/rexxref. Both "main" and "docs" are
in the same directory.
Josep Maria
Missatge de Sahananda del dia dj., 23 d’oct. 2025 a
les 14:57:
> It's a while since I used the SVN, but
It's a while since I used the SVN, but I just updated my working copy.
I've never applied a patch, but I thought I would give it a try.
My manual says
Open the patch and look at the first line to determine where it was created
from
Patch #349 has this first line:
*Index: trunk/rexxref/en-US/intro
Any takers, please?
---rony
On 20.10.2025 12:08, Rony G. Flatscher wrote:
Josep Maria has been so kind to come up with patches for some of the documentation bugs he found
and reported, here the from the documentation tracker notification e-mails:
Can someone with commit rights please be so
