This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: java.security.AlgorithmParamterGenerator.java
- From: "Raif S. Naffah" <raif at fl dot net dot au>
- To: tromey at redhat dot com
- Cc: GCC libjava patches <java-patches at gcc dot gnu dot org>
- Date: Fri, 7 Mar 2003 19:21:36 +1100
- Subject: Re: java.security.AlgorithmParamterGenerator.java
- References: <200303021715.11260.raif@fl.net.au> <87wujbzt92.fsf@fleche.redhat.com>
- Reply-to: raif at fl dot net dot au
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
On Friday 07 March 2003 15:38, Tom Tromey wrote:
> >>>>> "Raif" == Raif S Naffah <raif at fl dot net dot au> writes:
> Raif> this patch addresses JDK 1.4 compatibility.
>
> I spot-checked a few of these patches and nothing problematic stood
> out. Can you check them in to Classpath? I will put them in gcj.
ok. thanks.
> Raif> + * java.security.AlgorithmParameterGenerator: formatting +
> documentation
>
> We prefer reformatting to be done as a separate patch.
> This makes it easier to see the "real" changes.
noted. i'll separate them into two checkins. i'm also in the process
of writing Mauve tests for these patches.
q/ since most of these are for new methods and some for new classes and
interfaces, is there a special procedure to specify this in the Mauve
tests; ie. include the new tests iff the new classes/interfaces/methods
are checked out?
cheers;
rsn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique
iD8DBQE+aFaY+e1AKnsTRiERAw2SAJ4wuOhnLv/9mDMoEjJbgw/7BNXcZgCgiGVA
k5nsr9GL9pMcPFcDLjcu+yA=
=Dicp
-----END PGP SIGNATURE-----