From: Mark Wielaard <mark@klomp.org>
To: Dr Andrew John Hughes <ahughes@redhat.com>
Cc: Pavel Tisnovsky <ptisnovs@redhat.com>, mauve-discuss@sourceware.org
Subject: Re: RFC: fix for Mauve test javax/swing/JTextArea/prefferedSize.java
Date: Mon, 12 Sep 2011 09:13:00 -0000 [thread overview]
Message-ID: <1315818766.3367.1.camel@springer.wildebeest.org> (raw)
In-Reply-To: <20110907153511.GA18346@rivendell.middle-earth.co.uk>
On Wed, 2011-09-07 at 16:35 +0100, Dr Andrew John Hughes wrote:
> On 13:35 Wed 07 Sep , Pavel Tisnovsky wrote:
> I guess this is ok, but I have to admit I don't really know this GUI stuff that
> well. Would be good if someone else could take a look.
It does make sense to me to change the tests as Pavel suggests.
Cheers,
Mark
prev parent reply other threads:[~2011-09-12 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 14:15 Pavel Tisnovsky
2011-09-02 15:03 ` Dr Andrew John Hughes
2011-09-02 15:07 ` Pavel Tisnovsky
2011-09-07 2:39 ` Dr Andrew John Hughes
2011-09-07 11:34 ` Pavel Tisnovsky
2011-09-07 15:35 ` Dr Andrew John Hughes
2011-09-12 9:13 ` Mark Wielaard [this message]
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=1315818766.3367.1.camel@springer.wildebeest.org \
--to=mark@klomp.org \
--cc=ahughes@redhat.com \
--cc=mauve-discuss@sourceware.org \
--cc=ptisnovs@redhat.com \
/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).