From: Andrew Haley <aph@redhat.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: "classpath@gnu.org" <classpath@gnu.org>,
"Mark Wielaard" <mark@klomp.org>,
"Andrew Hughes" <gnu.andrew@redhat.com>,
Andïï <gnu_andrew@member.fsf.org>,
Andïï <gnu.andrew.rocks@gmail.com>,
"Mario Torre" <neugens@redhat.com>,
java@gcc.gnu.org
Subject: Re: Status of GNU Classpath
Date: Tue, 7 Feb 2023 10:34:49 +0000 [thread overview]
Message-ID: <228153ff-da90-ac9b-e191-fdac91baed62@redhat.com> (raw)
In-Reply-To: <87357i7tuf.fsf@elephly.net>
On 2/6/23 14:25, Ricardo Wurmus wrote:
> Hi Guillermo,
>
>> I can see that development halted around 2016 (from the commit logs of
>> the official git repo), but would like to know if someone else is
>> still using GNU Classpath.
> GNU Guix is using GNU Classpath in the bootstrap path from C to modern JDKs.
That's very cool. I wasn't aware that anyone was still doing this. It's important
to maintain a way to rebuild OpenJDK from scratch, with free software.
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2023-02-07 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABDcavY1sfVXs=zhF3fB+LS+HbszaDzs4KUzbkryFyz13ngtwQ@mail.gmail.com>
2023-02-06 12:55 ` Guillermo Rodriguez Garcia
2023-02-06 14:25 ` Ricardo Wurmus
2023-02-06 16:16 ` Guillermo Rodriguez Garcia
2023-02-08 10:42 ` Ricardo Wurmus
2023-02-08 15:55 ` Guillermo Rodriguez Garcia
2023-02-10 19:08 ` Ricardo Wurmus
2023-02-07 10:34 ` Andrew Haley [this message]
2023-02-07 10:55 ` Mark Wielaard
2023-02-07 10:47 ` Mark Wielaard
2023-02-07 13:00 ` Guillermo Rodriguez Garcia
2023-09-13 10:06 ` Guillermo Rodriguez Garcia
2023-09-14 8:15 ` Mark Wielaard
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=228153ff-da90-ac9b-e191-fdac91baed62@redhat.com \
--to=aph@redhat.com \
--cc=classpath@gnu.org \
--cc=gnu.andrew.rocks@gmail.com \
--cc=gnu.andrew@redhat.com \
--cc=gnu_andrew@member.fsf.org \
--cc=guille.rodriguez@gmail.com \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=neugens@redhat.com \
--cc=rekado@elephly.net \
/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).