From: Pekka Enberg <penberg@kernel.org>
To: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
Cc: "classpath@gnu.org" <classpath@gnu.org>, kgy <gykarsai@all.hu>,
"java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: Re: Re: GCJ ------ file type not supported by system
Date: Thu, 04 Sep 2014 20:07:00 -0000 [thread overview]
Message-ID: <CAOJsxLGQxnpmrkxCUQJJT3ZVZ8Zd2FT=1=-yfJjz6dnd+zCfBg@mail.gmail.com> (raw)
In-Reply-To: <CABDcavbXxFiqTenZm0DJ8MhT5TLOgiMDhGArRjB5wpuTzG7c-g@mail.gmail.com>
El jueves, 4 de septiembre de 2014, Pekka Enberg <penberg@kernel.org> escribió:
>> No, it's really not unfair at all. You are basically saying Andrew is
>> doing a crappy job as a maintainer
On Thu, Sep 4, 2014 at 10:29 PM, Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com> wrote:
> No, I am definitely NOT saying that, nothing even close. Please don't put
> your words in my mouth, thank you.
Of course you are saying that. Why else would you even bring up the
issue of finding a "competent successor" which implies that Andrew is
no longer interested in GNU Classpath and neglecting its maintenance?
El jueves, 4 de septiembre de 2014, Pekka Enberg <penberg@kernel.org> escribió:
>> Once you answer the hypothetical question *who* should
>> be the successor, you will understand why.
On Thu, Sep 4, 2014 at 10:29 PM, Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com> wrote:
> I see, so if I don't have the answer, the question makes no sense. Ok.
You didn't even try to answer the question, did you?
If Andrew actually needed a "competent successor" (he doesn't), what
is required of that person? The person needs to be an active
developer, needs to understand GNU Classpath well, and has to have
support from people who actually developed the project, right?
Are you able to make an educated guess who actually meets that criteria?
- Pekka
next prev parent reply other threads:[~2014-09-04 20:07 UTC|newest]
Thread overview: 29+ 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
[not found] ` <CABDcavbXxFiqTenZm0DJ8MhT5TLOgiMDhGArRjB5wpuTzG7c-g@mail.gmail.com>
2014-09-04 20:07 ` Pekka Enberg [this message]
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
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='CAOJsxLGQxnpmrkxCUQJJT3ZVZ8Zd2FT=1=-yfJjz6dnd+zCfBg@mail.gmail.com' \
--to=penberg@kernel.org \
--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).