From: Diego Novillo <dnovillo@google.com>
To: Olatunji Ruwase <tjruwase@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [plugin] Directory for plugins distributed with gcc
Date: Wed, 15 Jul 2009 18:43:00 -0000 [thread overview]
Message-ID: <b798aad50907151143v5abe42daj897861ed5591724c@mail.gmail.com> (raw)
In-Reply-To: <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com>
[ Moved to gcc@ ]
On Wed, Jul 15, 2009 at 14:30, Olatunji Ruwase<tjruwase@google.com> wrote:
> Has any decision being made on how plugins will be distributed with
> future releases. Is there going to be a plugins directory ?.
> Thanks
We may want to produce some plugins that are useful for GCC
development and distribute them with the compiler, but in general I
don't think we should get in the habit of incorporating 3rd party
plugins in GCC. This would be detrimental to one of the useful
properties of plugins (i.e., less code we need to maintain).
I set up a landing page where projects can register their plugins
(http://gcc.gnu.org/wiki/plugins). My suggestion is to use that page
as the central plugins directory, with the assumption that we (GCC)
are not the maintainers of those packages. We simply provide a link
to them.
Diego.
next parent reply other threads:[~2009-07-15 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fe7fd8170907151130j35ac3348kb447e7e1d273d9af@mail.gmail.com>
2009-07-15 18:43 ` Diego Novillo [this message]
2009-07-15 18:51 ` Olatunji Ruwase
2009-07-15 19:14 ` Diego Novillo
2009-07-15 19:36 ` Joseph S. Myers
2009-07-15 20:43 ` Paolo Bonzini
2009-07-15 20:53 ` Joseph S. Myers
2009-07-15 21:16 ` Basile STARYNKEVITCH
2009-07-15 21:43 ` Paolo Bonzini
2009-07-16 13:09 ` Rafael Espindola
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=b798aad50907151143v5abe42daj897861ed5591724c@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=tjruwase@google.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).