Hi David,
Could you look at this error?
Beginning work on en-US
Validation failed:
userdialog.xml:1126: validity error : Element varlistentry content
does not follow the DTD, expecting (term+ , listitem), got (term
indexterm indexterm listitem )
make: *** [pdf] Error 2
[miesfeld@Raven oodialog]$
On 29.08.2012 18:14, Rick McGuire wrote:
> Feels like being reunited with an old friend :-) Everything looks just like
> it did
> originally...even handled by my old filter correctly. Thanks for figuring
> this out!
Hear, hear!
Received the commit and the filter picked it up as if nothing had
Feels like being reunited with an old friend :-) Everything looks just
like it did originally...even handled by my old filter correctly. Thanks
for figuring this out!
Rick
On Wed, Aug 29, 2012 at 11:53 AM, Mark Miesfeld wrote:
> Ok, I just finished adding the svnnotify hook, and this came thr
Ok, I just finished adding the svnnotify hook, and this came through.
So, it looks like it is working.
I looked at the old commit notices and saw that the 'from' field was
the SourceForge user who made the commit, so the mailing list must
already be set up correctly for the committers.
Let me kno
On Wed, Aug 29, 2012 at 7:36 AM, Rick McGuire wrote:
> If these are the same notices we used to get, then I'm all for this change.
> Once this is done, is there a mechanism for turning off the allura notices
> that are sent to committers? I haven't seen any way of controlling that
> yet. I'm su
If these are the same notices we used to get, then I'm all for this change.
Once this is done, is there a mechanism for turning off the allura notices
that are sent to committers? I haven't seen any way of controlling that
yet. I'm sure I could just filter those to the bit bucket, but I'd prefer
SourceForge support says they have the svnnotify issue fixed. I'd
like to get the oorexx-svn mailing list working again.
If there are no objections, I'll work on it over the weekend.
We have to set up the hook ourselves, but SourceForge has a doc on it.
Looking at the hook I don't see any reaso
On 29.08.2012 12:02, Rony G. Flatscher wrote:
> On 29.08.2012 05:36, Mark Miesfeld wrote:
>> Hi All
>>
>> I moved main 4.1.2 from branches to releases and docs 4.1.2 from
>> branches to releases
>>
>> Things are set on on SourceForge:
>>
>> https://sourceforge.net/projects/oorexx/files/oorexx/4.1.
On 29.08.2012 05:36, Mark Miesfeld wrote:
> Hi All
>
> I moved main 4.1.2 from branches to releases and docs 4.1.2 from
> branches to releases
>
> Things are set on on SourceForge:
>
> https://sourceforge.net/projects/oorexx/files/oorexx/4.1.2/
>
> and
>
> https://sourceforge.net/projects/oorexx/f
