From: Lillian Angel <langel@redhat.com>
To: mauve-discuss@sourceware.org
Subject: DefaultStyledDocument.ElementBuffer regressions
Date: Fri, 03 Feb 2006 16:29:00 -0000 [thread overview]
Message-ID: <1138984187.5743.443.camel@tow.toronto.redhat.com> (raw)
Hello,
I submitted a final patch to Classpath to fix the ElementBuffer's
structure. The structure is correct for all the mauve tests in
gnu/testlet/javax/swing/text/DefaultStyledDocument/ElementBuffer.
There are still some regressions that are showing up. These are caused
because we are creating our elements differently than Sun (in a
different order or more elements are being created). Overall, these
should not be considered regressions, they should be changed to _just_
failures. They can be fixed later on.
The important thing is that the structure is correct for ElementBuffer.
Right now it works identical to Sun :)
Thanks,
Lillian
reply other threads:[~2006-02-03 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1138984187.5743.443.camel@tow.toronto.redhat.com \
--to=langel@redhat.com \
--cc=mauve-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).