public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mario Torre <neugens@redhat.com>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: Andrew Haley <aph@redhat.com>,
	"classpath@gnu.org" <classpath@gnu.org>,
	       kgy <gykarsai@all.hu>,
	"java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: GCJ ------ file type not supported by system
Date: Mon, 01 Sep 2014 10:47:00 -0000	[thread overview]
Message-ID: <1409568429.4242.1.camel@nirvana.localdomain> (raw)
In-Reply-To: <CABDcavZQ76W4sTm3rssD8UTWyCnD95Uo5BKon=8sFhRcNq5prA@mail.gmail.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


  reply	other threads:[~2014-09-01 10:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:00 kgy
2014-08-29  8:07 ` Fwd: " Andrew Haley
2014-08-29  8:34   ` Mario Torre
2014-08-29  9:47   ` Guillermo Rodriguez Garcia
2014-08-29  9:57     ` Mario Torre
2014-08-29 10:00       ` Guillermo Rodriguez Garcia
2014-09-01  9:03         ` Andrew Haley
2014-09-01  9:32           ` Guillermo Rodriguez Garcia
2014-09-01 10:47             ` Mario Torre [this message]
2014-09-03 16:12               ` Guillermo Rodriguez Garcia
2014-09-03 16:30                 ` Andrew Haley
2014-09-03 16:35                   ` Guillermo Rodriguez Garcia
2014-09-03 17:11                     ` Andrew Haley
2014-09-03 17:31                       ` Guillermo Rodriguez Garcia
2014-09-03 18:00                         ` Mark Wielaard
2014-09-03 19:00                           ` Guillermo Rodriguez Garcia
2014-09-03 17:59                     ` Per Bothner
2014-09-03 18:06                       ` Mark Wielaard
2014-09-04  8:14                       ` Andrew Haley
2014-09-04 20:37                         ` Per Bothner
2014-09-04 12:14                 ` Andïï
2014-09-04 16:17                   ` Guillermo Rodriguez
2014-09-04 18:54                     ` Pekka Enberg
     [not found]                       ` <CABDcavbXxFiqTenZm0DJ8MhT5TLOgiMDhGArRjB5wpuTzG7c-g@mail.gmail.com>
2014-09-04 20:07                         ` Pekka Enberg
2014-09-04 20:15                           ` Andrew Haley
2014-09-04 20:43                             ` Pekka Enberg
2014-09-04 21:35                     ` Mark Wielaard
2014-09-05  9:38                     ` Mario Torre
2014-09-05  9:39                     ` Mario Torre
  -- strict thread matches above, loose matches on Subject: below --
2014-08-28 14:30 kgy
2014-08-28 15:30 ` Bodo Thiesen

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=1409568429.4242.1.camel@nirvana.localdomain \
    --to=neugens@redhat.com \
    --cc=aph@redhat.com \
    --cc=classpath@gnu.org \
    --cc=guille.rodriguez@gmail.com \
    --cc=gykarsai@all.hu \
    --cc=java@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).