From: Dhek Bhun Kho <bhun@chello.nl>
To: rhug-rhats@sources.redhat.com
Subject: GCJ 3.2.1 - general question
Date: Mon, 30 Dec 2002 16:51:00 -0000 [thread overview]
Message-ID: <1041295904.13490.53.camel@tasslehof.bhun.net> (raw)
Hello there,
I know that the info page on rhug calls/suggests using gcj 3.3/cvs
versions, but if I get compilation errors with the current release of
gcc (3.2.1) and have a patch for it, should I post it?
greets,
Bhun.
reply other threads:[~2002-12-31 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1041295904.13490.53.camel@tasslehof.bhun.net \
--to=bhun@chello.nl \
--cc=rhug-rhats@sources.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).