public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Roman Kennke <roman@kennke.org>
Cc: mauve-discuss@sources.redhat.com, classpath@gnu.org
Subject: Re: Updating Mauve tags
Date: Mon, 16 Jan 2006 10:32:00 -0000	[thread overview]
Message-ID: <1137404915.5615.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1137369579.7846.32.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

Hi Roman,

On Mon, 2006-01-16 at 00:59 +0100, Roman Kennke wrote:
> The problem that I am seeing is when a test that is written to PASS
> under 1.4 fails under 1.5. There are lots of those tests in the
> testsuite for the javax.swing package.

To be honest, I would just remove those tests and concentrate on the 1.5
ones.

> So my plan would have been to tag
> all tests that pass under JDK1.5 with the 1.5 tag and those that don't
> only with JDK1.4 or whatever is ok. Since the tags are not meant to be
> used that way, maybe we can do it different. Could we extend the
> choose-classes script to detect !JDK1.x tags in the tag header of java
> source files and don't include the test in a JDK1.x test run?

I always thought it already worked that way (see the README), so if it
doesn't and you can make it actually do that then that would be great.

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-01-16 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-14 21:33 Roman Kennke
2006-01-15 22:08 ` Mark Wielaard
2006-01-15 23:59   ` Roman Kennke
2006-01-16 10:25     ` Meskauskas Audrius
2006-01-16 10:32     ` Mark Wielaard [this message]
2006-01-16 10:59     ` David Gilbert

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=1137404915.5615.14.camel@localhost.localdomain \
    --to=mark@klomp.org \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=roman@kennke.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).