From: Anthony Green <green@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: BCEL question
Date: Wed, 11 Dec 2002 20:31:00 -0000 [thread overview]
Message-ID: <1039667582.2883.59.camel@escape> (raw)
In-Reply-To: <873cp4hzyk.fsf@fleche.redhat.com>
On Wed, 2002-12-11 at 15:56, Tom Tromey wrote:
> What is the usual approach here?
> Find a new BCEL and see if it is fixed?
I think BCEL was just upgraded by Gary. Does a newer version exist?
> Fix BCEL in the rhug tree?
Don't hesitate to patch rhug. It contains a number of work-arounds
already.
AG
next prev parent reply other threads:[~2002-12-12 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 15:57 Tom Tromey
2002-12-11 20:31 ` Anthony Green [this message]
2002-12-16 10:44 ` Tom Tromey
2002-12-18 2:07 ` Gary Benson
2002-12-30 16:39 ` Dhek Bhun Kho
2003-01-05 0:01 ` rhino 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=1039667582.2883.59.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).