Re: [Oorexx-devel] New Process for Building the ooRexx Documentation, version 2

> Am 29.03.2020 um 01:15 schrieb Gil Barmwater : > > Once again I seem to have confused the folks I was trying to help . In > version 2, the folders fo_files and log_files are included and each contain a > single, one-line file names info.txt. This was supposed to eliminate the need > to

[Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

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.

Re: [Oorexx-devel] New Process for Building the ooRexx Documentation, version 2

Well, I had apparently decided that the PDF_files directory needed to be in the package because I had created the appropriate info.txt file but then forgot that it needed to go in the package :-[. I have now added the folder and file to both the delta folder and the package zip-file. I also

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

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

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

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 > Am 29.03.2020 um 17:32 schrieb Rick McGuire : > > Please DO NOT FORWARD these messages. The other messages indicating a commit > is made gets through

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

Hi P.O., Are you subscribed to the OoRexx-svn list ? 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

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

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 > ?  That wasn't one > of the ones that I > moderated for you

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

Dear Jon, I actually subscribed to ALL lists, twice, to get the confirmation that I was already subscribed… I will do it again and let you know Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 29.03.2020 um 18:04 schrieb Jon Wolfers : > > Hi P.O., > > Are you subscribed to

[Oorexx-devel] Fwd: Project Mailing List - Already Subscribed

Dear Jon, I followed your link and this is what I get back when I try to subscribe (again) Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Anfang der weitergeleiteten Nachricht: > > Von: SourceForge.net > Betreff: Project Mailing List - Already Subscribed > Datum: 29. März 2020

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

I, too, have gotten the " Your message has been rejected, probably because you are not subscribed to the mailing list and the list's policy is to prohibit non-members from posting to it. " message after doing the commit. I checked and the changes were committed, just no notification went out

Re: [Oorexx-devel] SF.net SVN: oorexx-code-0:[12018] main/trunk

> > We had to wrestle with this issue in the past, but I don't recall the > specific solution. I believe the issue here is that sourceforge uses your > sourceforge email address for posting the update emails, and that is what > is getting rejected. For example, emails from my commits show up as "

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

On 29.03.2020 19:23, Gil Barmwater wrote: > > Did you see mine for r12010 - the fix for the CSS issues? Gil > Hmm, as a matter of fact: no! These are the svn e-mails that I have received (I filter them to the same local mailbox as patches: ---rony ___

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

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

Re: [Oorexx-devel] SF.net SVN: oorexx-code-0:[12018] main/trunk

OK, being new committers, I would expect that our SF e-mail address would NOT be subscribed to the oorexx-svn list. I checked mine and I was not so I fixed it. Hopefully my next commit will get sent out to the list. Thanks Rick and P.O.! Gil On 3/29/2020 2:44 PM, P.O. Jonsson wrote: I think

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

Yes, I did! Gil On 3/29/2020 6:05 PM, P.O. Jonsson wrote: Dear all, I just did a commit 12023 re Changing readme to readme.txt in oorexx.spec.in  to fix broken rpm builds. Did you get it? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

Resubscribing told me that I have been already subscribed to: ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

Dear all, I just did a commit 12023 re Changing readme to readme.txt in oorexx.spec.in to fix broken rpm builds. Did you get it? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 29.03.2020 um 19:23 schrieb Gil Barmwater : > > Did you see mine for

Re: [Oorexx-devel] New Process for Building the ooRexx Documentation, version 2

I'll take a look. Thanks for including the .fo file as well. Gil On 3/29/2020 6:23 PM, P.O. Jonsson wrote: Dear Gil, I will have to postpone the testing of html to later in the week, I have some other things to attend to first, sorry about that. Before testing the new stuff I retested pdfs

Re: [Oorexx-devel] SF.net SVN: oorexx-code-0:[12018] main/trunk

Phew, not only me then :-) I think Jon needs to look into this. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 29.03.2020 um 20:13 schrieb Gil Barmwater : > > I, too, have gotten the " > > Your message has been rejected, probably because you are not > subscribed to the

Re: [Oorexx-devel] Fwd: SF.net SVN: oorexx-code-0:[12018] main/trunk

To be sure that they do not get filtered away I searched through all my e-mail folders for the string "[12010]" in subject without success. So that svn-e-mail has not arrived either, which is really strange. ---rony ___ Oorexx-devel mailing list

Re: [Oorexx-devel] SF.net SVN: oorexx-code-0:[12018] main/trunk

I think Rick cracked it. I now remember I originally registered with another Email originally (listed as inactive in my account on Sourceforge) I subscribed with that original Email to the list and I now I get the commit messages. @Rony and Gil: Log on to sourceforge account and check your