This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ ------ file type not supported by system
- From: Mario Torre <neugens at redhat dot com>
- To: Guillermo Rodriguez Garcia <guille dot rodriguez at gmail dot com>
- Cc: Andrew Haley <aph at redhat dot com>, "classpath at gnu dot org" <classpath at gnu dot org>, kgy <gykarsai at all dot hu>, "java at gcc dot gnu dot org" <java at gcc dot gnu dot org>
- Date: Mon, 01 Sep 2014 12:47:09 +0200
- Subject: Re: GCJ ------ file type not supported by system
- Authentication-results: sourceware.org; auth=none
- References: <B040B27C8A444D98B4F39FA5626D6022 at P5LD2Deluxe> <540034B0 dot 4010701 at redhat dot com> <CABDcavbBDFUcPKPXqL62xKp0iHzLFEGpcQsuRxZzgv=EDQJ8Dg at mail dot gmail dot com> <1409306247 dot 25913 dot 21 dot camel at nirvana dot localdomain> <CABDcavZaV7MtD9tHjzRpUU2zMsnuVoHMer1kUXPdNggAb_7hnA at mail dot gmail dot com> <54043670 dot 4070908 at redhat dot com> <CABDcavZQ76W4sTm3rssD8UTWyCnD95Uo5BKon=8sFhRcNq5prA at mail dot gmail dot com>
On Mon, 2014-09-01 at 11:32 +0200, Guillermo Rodriguez Garcia wrote:
> Hi Andrew,
>
> 2014-09-01 11:03 GMT+02:00 Andrew Haley <aph@redhat.com>:
> > On 29/08/14 11:00, Guillermo Rodriguez Garcia wrote:
> >> Yes I know that anyone can work on GNU Classpath. But as in any OSS
> >> project, a new project maintainer taking over "ownership" (in the OSS
> >> sense of the word) would need to have the approval and the support of
> >> the current maintainers.
> >
> > That would not be a problem. But really, there's no need to own
> > the project: all patches are welcome.
>
> Yes I am sure about this, but that is not my point. What I am saying
> is that it would be very good for the project to be maintained by a
> team who really wants to move things forward.
>
I understand what you mean, but the current maintainer has always
integrated patches and done releases, I think the problem is not the
lack of one maintainer willing to move forward, is lack of manpower to
do it.
As I said, anyone can step in, if patches start to flow (including bug
fixes) I'm sure they'll be integrated correctly and quickly.
If someone wants to take the project, the best thing to do is to start
contributing patches. After all, how can the maintainer know if someone
is seriously willing to take his role if there lack of a serious and
recent contribution flow?
Cheers,
Mario