From: Richard Guenther <richard.guenther@gmail.com>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: Diego Novillo <dnovillo@google.com>,
janis187@us.ibm.com,
"Joseph S. Myers" <joseph@codesourcery.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: "plugin"-ifying the MELT branch.
Date: Wed, 17 Jun 2009 10:49:00 -0000 [thread overview]
Message-ID: <84fc9c000906170349m4429999ck437d22b48263f607@mail.gmail.com> (raw)
In-Reply-To: <4A37D6B1.4010105@starynkevitch.net>
On Tue, Jun 16, 2009 at 7:30 PM, Basile
STARYNKEVITCH<basile@starynkevitch.net> wrote:
> Diego Novillo wrote:
>>
>> On Tue, Jun 16, 2009 at 13:10, Janis Johnson<janis187@us.ibm.com> wrote:
>>
>>
>>>
>>> Basile, people are saying that MELT no longer belongs in a branch of
>>> the GCC repository because now that plug-ins are supported, MELT no
>>> longer needs to modify GCC itself and can be maintained independently.
>
> MELT is not pluginified yet. So it will stay some time as a branch, because
> today it cannot be a plugin (for various small technical details).
My comment was to the new "branch" you were about to create where the
MELT plugin will materialize. And yes, Janis got it right.
Richard.
next prev parent reply other threads:[~2009-06-17 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 18:33 Basile STARYNKEVITCH
2009-06-05 16:14 ` Tom Tromey
2009-06-16 11:13 ` Basile STARYNKEVITCH
2009-06-16 11:16 ` Richard Guenther
2009-06-16 11:21 ` Basile STARYNKEVITCH
2009-06-16 11:38 ` Joseph S. Myers
2009-06-16 12:22 ` Basile STARYNKEVITCH
2009-06-16 12:53 ` Richard Guenther
2009-06-16 13:10 ` Joseph S. Myers
2009-06-16 17:10 ` Janis Johnson
2009-06-16 17:20 ` Diego Novillo
2009-06-16 17:30 ` Basile STARYNKEVITCH
2009-06-17 10:49 ` Richard Guenther [this message]
2009-06-17 11:56 ` Basile STARYNKEVITCH
2009-06-16 17:33 ` Joseph S. Myers
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=84fc9c000906170349m4429999ck437d22b48263f607@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=basile@starynkevitch.net \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=joseph@codesourcery.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).