On 30.03.2020 00:05, P.O. Jonsson wrote:
> I just did a commit 12023 re Changing readme to readme.txt in oorexx.spec.in
> <http://oorexx.spec.in> to fix broken rpm builds. Did you get it?

Although I did get an e-mail now, interestingly there are still problems with 
its e-mail header:

    From:  Open Object Rexx SVN repository  
<*noreply@code-0**.oorexx.p.re*.sourceforge.net>
    To: Open Object Rexx SVN repository  
*<noreply@code-0**.oorexx.p.re*.sourceforge.net>
    Reply-To: Open Object Rexx SVN repository 
<*nore...@code-0.oorexx.p.re*.sourceforge.net>

    Subject: *[oorexx:code-0]* New commit [r12023] by perolovjonsson

whereas the svn commit messages usually have the following e-mail header, e.g. :

    From:  orexx--- via Oorexx-svn <*oorexx-svn@lists*.sourceforge.net>
    To: *oorexx-svn@lists*.sourceforge.net
    Reply-To: *oorexx-svn@lists*.sourceforge.net
    Cc: or...@users.sf.net

    Subject: *[Oorexx-svn*] SF.net SVN: oorexx-code-0:[12022] 
docs/trunk/rexxpg/en-US/provide.xml

Although I can adjust my filter to also move *[oorexx:code-0]* to svn it would 
be better, if it
became possible to change it such that *[oorexx-svn]* will be the tag. Also the 
automatically
created *[Oorexx-svn]* subject is more precise in that it hints at the first 
file name that got changed.

No clues how to go about it though.

---rony



> Am 29.03.2020 um 19:23 schrieb Gil Barmwater <gbarmwa...@alum.rpi.edu
> <mailto:gbarmwa...@alum.rpi.edu>>:
>>
>> Did you see mine for r12010 - the fix for the CSS issues? Gil
>>
>> On 3/29/2020 12:07 PM, Rony G. Flatscher wrote:
>>>
>>> That is really strange: I see all commits except for P.O.'s commits!
>>>
>>> ---rony
>>>
>>>
>>> On 29.03.2020 18:04, Jon Wolfers wrote:
>>>> Hi P.O.,
>>>>
>>>> Are you subscribed to the OoRexx-svn list
>>>> <https://sourceforge.net/projects/oorexx/lists/oorexx-svn>?  That wasn't 
>>>> one of the ones that I
>>>> moderated for you the other day.
>>>>
>>>> (Due to world madness - Moderators can no longer see the names of 
>>>> subscribers to sourceforge
>>>> mailing lists)
>>>>
>>>> Jon
>>>>
>>>> On Sun, 29 Mar 2020 at 16:43, P.O. Jonsson <oor...@jonases.se 
>>>> <mailto:oor...@jonases.se>> wrote:
>>>>
>>>>     Ok, thanks for the hint, I cannot see that the info gets through 
>>>> myself. Sorry.
>>>>
>>>>     Hälsningar/Regards/Grüsse,
>>>>     P.O. Jonsson
>>>>     oor...@jonases.se <mailto:oor...@jonases.se>
>>>>
>>>>
>>>>
>>>>>     Am 29.03.2020 um 17:32 schrieb Rick McGuire <object.r...@gmail.com
>>>>>     <mailto:object.r...@gmail.com>>:
>>>>>
>>>>>     Please DO NOT FORWARD these messages. The other messages indicating a 
>>>>> commit is made gets
>>>>>     through and includes a link to the relevant commit information if we 
>>>>> need to see it. You
>>>>>     taking an extra step to forward them defeats the filters I have set 
>>>>> up for dealing with
>>>>>     commit messages. The extra noise is not appreciated. 
>>>>>
>>>>>     Rick
>>>>>
>>>>>     On Sun, Mar 29, 2020 at 11:05 AM P.O. Jonsson <oor...@jonases.se
>>>>>     <mailto:oor...@jonases.se>> wrote:
>>>>>
>>>>>         Dear all,
>>>>>
>>>>>         For some reason my (automated) messages to oorexx-svn list are 
>>>>> rejected. The committed
>>>>>         items go through but until this issue is solved I will forward 
>>>>> the messages here.
>>>>>         Sorry for spamming but I do not know what else to do, I am 
>>>>> subscribed to the list afaik.
>>>>>
>>>>>         Hälsningar/Regards/Grüsse,
>>>>>         P.O. Jonsson
>>>>>         oor...@jonases.se <mailto:oor...@jonases.se>
>>>>>
>>>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to