From: Jon VanAlten <jon.vanalten@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: GCJ-patches <java-patches@gcc.gnu.org>,
Jon VanAlten <jon.vanalten@redhat.com>,
classpath@gnu.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] update ecj to ecj-3.8.2/4.2.2
Date: Mon, 15 Apr 2013 14:44:00 -0000 [thread overview]
Message-ID: <439454453.517225.1366037089130.JavaMail.root@redhat.com> (raw)
In-Reply-To: <516BD4B9.8040101@ubuntu.com>
----- Original Message -----
> From: "Matthias Klose" <doko@ubuntu.com>
> To: "GCJ-patches" <java-patches@gcc.gnu.org>
> Cc: "Jon VanAlten" <jon.vanalten@redhat.com>, classpath@gnu.org, "Tom Tromey" <tromey@redhat.com>
> Sent: Monday, April 15, 2013 6:21:45 AM
> Subject: [patch] update ecj to ecj-3.8.2/4.2.2
>
> It looks like this ecj is already used
> within the Fedora disto, however only locally patched (at least I couldn't
> find
> any mail sent to java-patches).
>
My bad. I honestly didn't have any idea what the upstream process would be. My
history in the free java world starts after openjdk/icedtea, so all the gcj
fluff isn't really known well to me, and I don't really know where to look for
information (pointers appreciated! :D ). So I sort of let it slip through
the cracks.
I did bring it up on an earlier thread[1], and it seems like by accident it
also went to java-patches. Now I know for next time, if and when there is a
next time.
cheers,
jon
[1] http://mail.openjdk.java.net/pipermail/distro-pkg-dev/2013-March/022168.html
next prev parent reply other threads:[~2013-04-15 14:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 10:21 Matthias Klose
2013-04-15 13:29 ` Andrew Hughes
2013-04-15 13:50 ` Matthias Klose
2013-04-15 14:02 ` Andrew Hughes
2013-04-15 14:08 ` Matthias Klose
2013-04-15 14:22 ` Andrew Hughes
2013-04-15 14:44 ` Jon VanAlten [this message]
2013-04-15 21:34 ` Andrew Hughes
2013-04-15 22:39 ` Jon VanAlten
2013-06-20 12:39 ` ping: " Matthias Klose
2013-06-26 19:23 ` Jon VanAlten
2013-07-02 9:36 ` Matthias Klose
2013-07-02 19:04 ` Jon VanAlten
2013-12-10 15:51 ` Matthias Klose
2013-12-10 16:05 ` Andrew Haley
2013-12-10 16:23 ` Matthias Klose
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=439454453.517225.1366037089130.JavaMail.root@redhat.com \
--to=jon.vanalten@redhat.com \
--cc=classpath@gnu.org \
--cc=doko@ubuntu.com \
--cc=java-patches@gcc.gnu.org \
--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).