From: Pekka Enberg <penberg@kernel.org>
To: Guillermo Rodriguez <guille.rodriguez@gmail.com>
Cc: Andïï <gnu_andrew@member.fsf.org>,
"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: Thu, 04 Sep 2014 18:54:00 -0000 [thread overview]
Message-ID: <CAOJsxLFWJ8QRnFJaP4PCts+E6sy0dGHFPRW5_Ad56hAbFZ4aSw@mail.gmail.com> (raw)
In-Reply-To: <54089094.5080907@gmail.com>
On Thu, Sep 4, 2014 at 7:17 PM, Guillermo Rodriguez
<guille.rodriguez@gmail.com> wrote:
> I think that asking to "help rather than complain" is a bit unfair.
No, it's really not unfair at all. You are basically saying Andrew is
doing a crappy job as a maintainer when in reality he's pretty much
the only one developing GNU Classpath these days...
On Thu, Sep 4, 2014 at 7:17 PM, Guillermo Rodriguez
<guille.rodriguez@gmail.com> wrote:
> First of all I am not "complaining", I am trying to suggest that perhaps,
> if time and resources are limited, the best way to spend them would be to
> look for a successor.
Thanks for the suggestion. We're going to just ignore it because it
makes no sense. Once you answer the hypothetical question *who* should
be the successor, you will understand why.
On Thu, Sep 4, 2014 at 7:17 PM, Guillermo Rodriguez
<guille.rodriguez@gmail.com> wrote:
> Second, I am willing to help in any way I can, and already stated that.
> Yes I can submit patches (and will do) although in my opinion this does
> not address the underlying problem. I think that updating the website
> (to help raise awareness and attract developers) would be much more
> useful than sending patches to fix bugs or issues.
I also think the website needs fixing. Are sources to it available
somewhere and who is able to update it if someone actually sends a
patch against it?
- Pekka
next prev parent reply other threads:[~2014-09-04 18:54 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
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 [this message]
[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=CAOJsxLFWJ8QRnFJaP4PCts+E6sy0dGHFPRW5_Ad56hAbFZ4aSw@mail.gmail.com \
--to=penberg@kernel.org \
--cc=classpath@gnu.org \
--cc=gnu_andrew@member.fsf.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).