You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by la...@apache.org on 1999/02/21 01:58:47 UTC

Re: os-other/2320: Support of UTS 2.1.2 is broken

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]


Synopsis: Support of UTS 2.1.2 is broken

State-Changed-From-To: open-feedback
State-Changed-By: lars
State-Changed-When: Sat Feb 20 16:58:47 PST 1999
State-Changed-Why:
[This is a standard response.]
This Apache problem report has not been updated recently.
Please reply to this message if you have any additional
information about this issue, or if you have answers to
any questions that have been posed to you.  If there are
no outstanding questions, please consider this a request
to try to reproduce the problem with the latest software
release, if one has been made since last contact.  If we
don't hear from you, this report will be closed.
If you have information to add, BE SURE to reply to this
message and include the apbugs@Apache.Org address so it
will be attached to the problem report!

Re: os-other/2320: Support of UTS 2.1.2 is broken

Posted by dw...@ihgp.ih.lucent.com.
On Feb 21, 12:58am, lars@apache.org wrote:
> Synopsis: Support of UTS 2.1.2 is broken
> 
> State-Changed-From-To: open-feedback
> State-Changed-By: lars
> State-Changed-When: Sat Feb 20 16:58:47 PST 1999
> State-Changed-Why:
> [This is a standard response.]
> This Apache problem report has not been updated recently.
> Please reply to this message if you have any additional
> information about this issue, or if you have answers to
> any questions that have been posed to you.  If there are
> no outstanding questions, please consider this a request
> to try to reproduce the problem with the latest software
> release, if one has been made since last contact.  If we
> don't hear from you, this report will be closed.
> If you have information to add, BE SURE to reply to this
> message and include the apbugs@Apache.Org address so it
> will be attached to the problem report!

As far as I can tell this was fixed already in 1.3.3.  Anyway,
I just tested it again in 1.3.4 and it works fine.

- Dave Dykstra