From: Anthony Green <green@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: more bugs
Date: Wed, 18 Dec 2002 17:18:00 -0000 [thread overview]
Message-ID: <1040260780.1981.285.camel@escape> (raw)
In-Reply-To: <87wum6zvoq.fsf@fleche.redhat.com>
On Wed, 2002-12-18 at 16:41, Tom Tromey wrote:
> There doesn't appear to be a `de' directory anywhere in rhug.
We're in the middle of rev'ing many of the packages in rhug.
The "de" package comes from the old version of BCEL. It has since
changed to org.apache.something since the Apache group took over
maintenance for BCEL.
Xalan needs to be rev'd now, but that depends on rev'ing Xerces, which
is stuck on this org.xml/org.w3c problem in the current gcj sources.
Can I submit a libgcj patch to simply extract org.xml and org.w3c into
their own libraries and leave it at that for now?
AG
next prev parent reply other threads:[~2002-12-19 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 16:41 Tom Tromey
2002-12-18 17:18 ` Anthony Green [this message]
2002-12-18 17:23 ` Tom Tromey
2002-12-18 18:28 ` Anthony Green
2002-12-18 17:52 ` Dhek Bhun Kho
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=1040260780.1981.285.camel@escape \
--to=green@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
--cc=tromey@redhat.com \
/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).