This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: more doc typos
- From: Tom Tromey <tromey at redhat dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, java-patches at gcc dot gnu dot org, GNU Classpath Patches <classpath-patches at gnu dot org>
- Date: Mon, 28 Jan 2008 08:53:37 -0700
- Subject: Re: more doc typos
- References: <20080124181804.GE14722@ins.uni-bonn.de> <Pine.LNX.4.64.0801272229090.4453@acrux.dbai.tuwien.ac.at>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Gerald" == Gerald Pfeifer <gerald@pfeifer.com> writes:
>> libjava/classpath/ChangeLog:
>> 2008-01-24 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
>> * doc/README.jaxp: Fix typos.
Gerald> I committed this on your behalf so that this will be in GCC
Gerald> 4.3.0, but you may also want to Cc: java-patches@gcc.gnu.org
Gerald> for anything Java-related.
In particular, changes in classpath/ usually should go upstream as
well.
I'm checking this fix into Classpath.
Tom
>> Index: libjava/classpath/doc/README.jaxp
>> ===================================================================
>> --- libjava/classpath/doc/README.jaxp (Revision 131766)
>> +++ libjava/classpath/doc/README.jaxp (Arbeitskopie)
>> @@ -155,7 +155,7 @@
>> When using libxmlj, the libxmlj shared library must be available.
>> In general it is picked up by the runtime using GNU Classpath. If not you
>> might want to try adding the directory where libxmlj.so is installed
>> -(by default ${prefix}/lib/classpath/) with ldconfig or specifing in the
>> +(by default ${prefix}/lib/classpath/) with ldconfig or specifying in the
>> LD_LIBRARY_PATH environment variable. Additionally, you may need to specify
>> the location of your shared libraries to the runtime environment using the
>> java.library.path system property.
>> @@ -174,7 +174,7 @@
>> using thread context variables.
>>
>> Update: thread context variables have been introduced. This is very
>> -untested though, libxmll therefore still has the single thread
>> +untested though, libxmlj therefore still has the single thread
>> bottleneck.