public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Mario Torre <neugens@redhat.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: Re: GCJ ------ file type not supported by system
Date: Fri, 29 Aug 2014 10:00:00 -0000	[thread overview]
Message-ID: <CABDcavZaV7MtD9tHjzRpUU2zMsnuVoHMer1kUXPdNggAb_7hnA@mail.gmail.com> (raw)
In-Reply-To: <1409306247.25913.21.camel@nirvana.localdomain>

Hi Mario,

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.

Guillermo

2014-08-29 11:57 GMT+02:00 Mario Torre <neugens@redhat.com>:
> On Fri, 2014-08-29 at 11:47 +0200, Guillermo Rodriguez Garcia wrote:
>> That is a pity.
>>
>> I think GNU Classpath is a very good choice for embedded systems with
>> limited flash/RAM (especially the latter).
>>
>> Perhaps it is time to look for adopters to take care of the project?
>> It would be really bad to let it just die.
>>
>> Guillermo
>
> Hi Guillermo,
>
> It's free software, anyone can step in :)
>
> Cheers,
> Mario
>
>



-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

  reply	other threads:[~2014-08-29 10:00 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 [this message]
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
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=CABDcavZaV7MtD9tHjzRpUU2zMsnuVoHMer1kUXPdNggAb_7hnA@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=aph@redhat.com \
    --cc=classpath@gnu.org \
    --cc=gykarsai@all.hu \
    --cc=java@gcc.gnu.org \
    --cc=neugens@redhat.com \
    /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).