From: Roger Sayle <roger@eyesopen.com>
To: Andrew Haley <aph@redhat.com>
Cc: java-patches@gcc.gnu.org, <classpath-patches@gnu.org>
Subject: Re: [JAVA] /bin/sh portability issues in gen-classlist.sh.in
Date: Fri, 07 Jul 2006 12:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0607070626320.14880-100000@www.eyesopen.com> (raw)
In-Reply-To: <17582.9450.511797.447785@zebedee.pink>
On Fri, 7 Jul 2006, Andrew Haley wrote:
> These seem mostly to be patches for the upstream Classpath library
> that is periodically merged into libgcj. We need to make sure that
> they are submitted there,
>
> classpath-patches@gnu.org
My apologies to the classpath-patches folks. I did check the
recent postings to the java-patches list, but I couldn't find a
crosspost mentioning where classpatch patches should be directed.
For those classpatch folks who don't read the java list, two out
of four of my recent series of patches to support building GCC on
i386-pc-solaris2.10 using the native /bin/sh affect classpatch
code, and as mentioned by Andrew above should be reviewed
upstream.
I'm happy to repost them to the classpatch-patches list if that's
required. But the original postings can be found at:
http://gcc.gnu.org/ml/gcc-patches/2006-07/msg00293.html
http://gcc.gnu.org/ml/gcc-patches/2006-07/msg00294.html
Sorry for the inconvenience,
Roger
--
next prev parent reply other threads:[~2006-07-07 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 4:32 Roger Sayle
2006-07-07 9:10 ` Andrew Haley
2006-07-07 12:59 ` Roger Sayle [this message]
2006-07-07 13:08 ` Andrew Haley
2006-07-07 10:14 ` Eric Botcazou
2006-07-07 13:36 ` Roger Sayle
2006-07-07 13:44 ` Eric Botcazou
2006-07-07 13:33 ` Paolo Bonzini
2006-07-08 0:57 ` Andrew Pinski
2006-07-08 1:17 ` Ralf Wildenhues
2006-08-18 19:48 ` Tom Tromey
2006-08-24 12:46 ` Roger Sayle
2006-10-10 17:10 ` Tom Tromey
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=Pine.LNX.4.44.0607070626320.14880-100000@www.eyesopen.com \
--to=roger@eyesopen.com \
--cc=aph@redhat.com \
--cc=classpath-patches@gnu.org \
--cc=java-patches@gcc.gnu.org \
/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).