This is the mail archive of the java-patches@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]

Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)

To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
Subject: Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
From: Tom Tromey <tromey at redhat dot com>
Date: 01 Aug 2001 22:20:44 -0600
Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
References: <15201.42919.330120.774610@xayide.TechFak.Uni-Bielefeld.DE> <87hevyhvx1.fsf@creche.redhat.com> <15206.65454.82631.821537@xayide.TechFak.Uni-Bielefeld.DE> <87ae1k3lm7.fsf@creche.redhat.com> <15208.19352.835699.59808@xayide.TechFak.Uni-Bielefeld.DE>
Reply-To: tromey at redhat dot com

>>>>> "Rainer" == Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> writes:

Rainer> So it looks like a global-write-privs maintainer is required
Rainer> for the gcc.c part, the alpha maintainer for the change to
Rainer> osf.h, and either Alex or Per for the gcc/java parts ;-(

That's typical for patches that span different parts of gcc.
My (limited) experience has been that persistence pays off.

Tom

References:
- 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
  - From: Rainer Orth
- Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
  - From: Tom Tromey
- Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
  - From: Rainer Orth
- Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
  - From: Tom Tromey
- Re: 3.0.1 PATCH: Allow jvgenmain to work with ASM_FINAL_SPEC (version 2)
  - From: Rainer Orth

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