On Sun, Sep 11, 2016 at 01:08:56PM +0100, Andrew Haley wrote:
> On 10/09/16 12:59, NightStrike wrote:
> > Could we at least reach out and see if there's someone else who could
> > be the maintainer? I noticed gcj patches recently, so there's still
> > interest.
>
> 1. It's too late. We have been discussing this for a long time, and
> we're now doing what we decided.
>
> 2. Maintaining GCJ requires a lot of knowledge of both Java and GCC
> internals. There are very few people in the world with that
> knowledge, and I'm fairly sure I know them by name.
>
> 3. The Classpath library is very old and is unmaintained. The only
> practical way to update GCJ would be to use the OpenJDK class
> libraries instead, but updating GCJ to use those class libraries is a
> very substantial job.
>
> So, I cannot prevent anyone from coming along to maintain GCJ, and
> neither would I want to. However, such a proposal would have to be
> credible. It is a multi-engineer-year commitment, and not just any
> ordinary engineers.
Can we move forward with this patch, then?
Marek
