This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: FYI: Updating makemake (Was: Importing new classpath)

From: David Daney <ddaney at avtrex dot com>
To: tromey at redhat dot com
Cc: Mark Wielaard <mark at klomp dot org>, GCJ Hackers <java at gcc dot gnu dot org>
Date: Tue, 08 Nov 2005 10:35:18 -0800
Subject: Re: FYI: Updating makemake (Was: Importing new classpath)
References: <1131302302.8469.70.camel@localhost.localdomain> <m3oe4wmqpy.fsf@localhost.localdomain> <1131461783.7570.16.camel@localhost.localdomain> <m3irv3dkmd.fsf@localhost.localdomain>

Tom Tromey wrote:

I moved this from the patch list.

Mark> So, who is going to do the actual import?

Good question. Usually I do.
Mark> What kind of feedback/extra testing do we need before it can be
Mark> done?
Where, if anywhere, do we think it is likely to break?
Did you need any patches other than the one to makemake.tcl?  If not,
that is a good sign.

The changes I checked in to mauve-libgcj yesterday are needed to run mauve against classpath (HEAD). I have been running the testsuite against classpath (HEAD) for the last couple of days, and it runs so that is good. However I didn't make a baseline run before I switched to the new classpath so I don't know if there are any regressions.

David Daney.

Follow-Ups:
- Re: FYI: Updating makemake (Was: Importing new classpath)
  - From: Mark Wielaard
- Re: FYI: Updating makemake (Was: Importing new classpath)
  - From: Tom Tromey

References:
- Importing new classpath
  - From: Mark Wielaard
- Re: Importing new classpath
  - From: Tom Tromey
- Re: FYI: Updating makemake (Was: Importing new classpath)
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]