public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Thomas Zander <zander@javalobby.org>, mauve-discuss@sources.redhat.com
Subject: Re: Some issues..
Date: Fri, 16 Apr 2004 09:31:00 -0000	[thread overview]
Message-ID: <16511.42905.101387.569375@cuddles.cambridge.redhat.com> (raw)
In-Reply-To: <1082067738.1986.49.camel@elsschot.wildebeest.org>

Mark Wielaard writes:
 > Hi,
 > 
 > On Sat, 2004-04-03 at 17:41, Andrew Haley wrote:
 > > Thomas Zander writes:
 > >  > Second; I found at least one directory that contains java files without a
 > >  > package; leading it to be uncompilable (due to duplicate class names)
 > >  > I found:
 > >  > gnu/testlet/BinaryCompatibility/altered/
 > >  > Should those have package lines??
 > > 
 > > No.  This package comes with a script that does the building and
 > > copies some files around.  I suppose you could create a Ant version of
 > > this script.
 > 
 > Which script is this? 

Err, the one in the BinaryCompatibility directory...

It's called `foo', of course!  :-)

 > Is it documented?

Yeah, right.

 > Might it be a good idea to add these tests to a separate module
 > like the visual tester and the verifier tests since they are
 > actually different from the rest of the mauve core library tests?

Can you please be a little more specific about this?

Andrew.

  reply	other threads:[~2004-04-16  9:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-03 13:05 Thomas Zander
2004-04-03 13:16 ` Andrew Haley
2004-04-03 13:41   ` Thomas Zander
2004-04-03 15:42     ` Andrew Haley
2004-04-03 16:06       ` Thomas Zander
2004-04-15 22:22       ` Mark Wielaard
2004-04-16  9:31         ` Andrew Haley [this message]
2004-04-16 11:29           ` Mark Wielaard
2004-04-16 12:01             ` Some issues.. (batch_run and runner script documentation) Mark Wielaard
2004-04-16 12:04             ` Some issues Andrew Haley
2004-04-22 21:41               ` Mark Wielaard
2004-04-15 22:14 ` Mark Wielaard
2004-05-07 11:54 ` John Leuner
2004-05-07 13:25   ` Thomas
2004-04-23  9:12 Jeroen Frijters
2004-04-25 11:10 ` Mark Wielaard
2004-04-29 11:41   ` Andrew Haley
2004-04-29 13:16     ` Thomas
2004-04-29 15:29       ` Andrew Haley
2004-05-01  9:49         ` Thomas Zander
2004-05-02 12:27           ` Andrew Haley

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=16511.42905.101387.569375@cuddles.cambridge.redhat.com \
    --to=aph@redhat.com \
    --cc=mark@klomp.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=zander@javalobby.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).