Re: "plugin"-ifying the MELT branch.

2009-06-17 Thread Basile STARYNKEVITCH
Richard Guenther wrote: On Tue, Jun 16, 2009 at 7:30 PM, Basile STARYNKEVITCH wrote: Diego Novillo wrote: On Tue, Jun 16, 2009 at 13:10, Janis Johnson wrote: Basile, people are saying that MELT no longer belongs in a branch of the GCC repository because now that plug-ins are s

Re: "plugin"-ifying the MELT branch.

2009-06-17 Thread Richard Guenther
On Tue, Jun 16, 2009 at 7:30 PM, Basile STARYNKEVITCH wrote: > Diego Novillo wrote: >> >> On Tue, Jun 16, 2009 at 13:10, Janis Johnson 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 >>

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Joseph S. Myers
On Tue, 16 Jun 2009, Janis Johnson 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. > That does not mean that MELT cannot be a

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Basile STARYNKEVITCH
Diego Novillo wrote: On Tue, Jun 16, 2009 at 13:10, Janis Johnson 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 n

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Diego Novillo
On Tue, Jun 16, 2009 at 13:10, Janis Johnson 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. > That does not mean that MELT c

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Janis Johnson
On Tue, 2009-06-16 at 14:22 +0200, Basile STARYNKEVITCH wrote: > I (Basile) very probably misunderstood what Joseph Myers or Richard > Guenther meant. What I might have [mis]understood scares me. This is a > request for clarification. > Did I understood that in your view no branch hosted on GCC

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Joseph S. Myers
On Tue, 16 Jun 2009, Basile STARYNKEVITCH wrote: > > > I thought on the contrary that is was expected that some code would become > > > FSF > > > owned plugins? > > > > > > > Not without a mechanism for linking plugins in statically on hosts for which > > we don't support dynamic loading of

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Richard Guenther
On Tue, Jun 16, 2009 at 2:22 PM, Basile STARYNKEVITCH wrote: > > I (Basile) very probably misunderstood what Joseph Myers or Richard Guenther > meant. What I might have [mis]understood scares me. This is a request for > clarification. > > > Joseph S. Myers wrote: > > >> On Tue, 16 Jun 2009, Basile

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Basile STARYNKEVITCH
I (Basile) very probably misunderstood what Joseph Myers or Richard Guenther meant. What I might have [mis]understood scares me. This is a request for clarification. Joseph S. Myers wrote: On Tue, 16 Jun 2009, Basile STARYNKEVITCH wrote: I thought on the contrary that is was expected

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Joseph S. Myers
On Tue, 16 Jun 2009, Basile STARYNKEVITCH wrote: > I thought on the contrary that is was expected that some code would become FSF > owned plugins? Not without a mechanism for linking plugins in statically on hosts for which we don't support dynamic loading of plugins, and even then it's doubtfu

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Basile STARYNKEVITCH
Richard Guenther wrote: On Tue, Jun 16, 2009 at 1:13 PM, Basile STARYNKEVITCH wrote: Basile STARYNKEVITCH wrote: Can a branch be simply a plugin, or should I close (soon) the melt-branch and start a melt-plugin-branch on the SVN. If I do that, do I need some authorization? from whom?

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Richard Guenther
On Tue, Jun 16, 2009 at 1:13 PM, Basile STARYNKEVITCH wrote: > Basile STARYNKEVITCH wrote: >> >> >> Can a branch be simply a plugin, or should I close (soon) the melt-branch >> and start a melt-plugin-branch on the SVN. If I do that, do I need some >> authorization? from whom? > > > Apparently, not

Re: "plugin"-ifying the MELT branch.

2009-06-16 Thread Basile STARYNKEVITCH
Basile STARYNKEVITCH wrote: Can a branch be simply a plugin, or should I close (soon) the melt-branch and start a melt-plugin-branch on the SVN. If I do that, do I need some authorization? from whom? Apparently, nothing very special is required to start a new branch. So I intend to creat

Re: "plugin"-ifying the MELT branch.

2009-06-05 Thread Tom Tromey
> "Basile" == Basile STARYNKEVITCH writes: Basile> Can a branch be simply a plugin, or should I close (soon) the Basile> melt-branch and start a melt-plugin-branch on the SVN. If I do that, Basile> do I need some authorization? from whom? I think what you do on your branch is up to you. If

"plugin"-ifying the MELT branch.

2009-06-04 Thread Basile STARYNKEVITCH
Hello All, To make MELT more interesting & more easy to use, I want to make it become a (big & meta *) plugin. I also need to document & illustrate it much more. I actually did start to work on the pluginification of MELT: I mean making MELT a real GCC plugin, not needing any core GCC patch a