I have provided the patch and will wait with the next step until that is in the 
system.

I have found more things that influences the documentation, I will let you know 
when I have done the complete analysis. I will try to do things sequentually 
this time, please bear with me for spamming you.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Am 19.03.2020 um 11:38 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
> 
> Dear P.O.,
> 
> updating the readme should be o.k. in any case as it is a documentation 
> improvement.
> 
> Cheers
> ---rony
> On 16.03.2020 21:41, P.O. Jonsson wrote:
>> Dear Rony,
>> 
>> Re
>>> Am 16.03.2020 um 20:18 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at 
>>> <mailto:rony.flatsc...@wu.ac.at>>:
>>> 
>>>> I can offer to include them in the readme and file a patch request to that 
>>>> effect. Is that ok or
>>>> does anyone have objections?
>>> 
>>> I think that makes sense and no one would have any objections, it is part 
>>> of the surrounding
>>> documentation for ooRexx.
>> 
>> Ok I will go ahead and make the changes and provide the patch request.
>> 
>> There are eight blanks at the beginning of each line in readme, I will 
>> remove those to give more room for the actual text if no-one objects.
>> 
>> I would like to rename readme to readme.txt. Currently macOS recognises 
>> readme as an executable, but that requires a minor patch to cmakelists.txt 
>> (that I can provide). Again if there is anyone against this change I will 
>> not do it.
>> 
>> /P.O.
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to