This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [plugins] Branch for plugins development created
- From: Diego Novillo <dnovillo at google dot com>
- To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
- Cc: gcc at gcc dot gnu dot org, Sean Callanan <spyffe at cs dot sunysb dot edu>, Taras Glek <tglek at mozilla dot com>, Le-Chun Wu <lcwu at google dot com>, Grigori Fursin <grigori dot fursin at inria dot fr>, Gerald Pfeifer <gerald at pfeifer dot com>
- Date: Fri, 6 Feb 2009 16:13:04 -0500
- Subject: Re: [plugins] Branch for plugins development created
- References: <b798aad50902061249o5bb3b83dr8edbd1381f997633@mail.gmail.com> <498CA5C1.50505@starynkevitch.net>
On Fri, Feb 6, 2009 at 16:04, Basile STARYNKEVITCH
<basile@starynkevitch.net> wrote:
> But given that most people agree that (since the plugin idea is not too
> ambitious) the plugin effort is not a big one (e.g. much much smaller than
> your heroic old-gimple => tuple work) why did'nt you consider accepting
> plugin related stuff into trunk?
Because we are not in stage 1. Unless a patch is very small, carrying
it around is a hassle, particularly when the group of folks interested
in testing it out is large as in this case.
> Or is the current stage of the trunk still in a phase where plugin related
> stuff are not accepted?
Right.
> My point is that by creating a plugin branch, we have to duplicate the
> review effort, since every thing has to be reviewed twice (once to be
> admittted into the plugin branch; once to be transported from plugin branch
> to trunk). And review time (& reviewers effort) is the most scare resource
> in GCC.
There will be additional review when the merge is proposed, but given
the review during the lifetime of the branch, it should not take too
long. I will propose merging the branch into mainline during the next
stage 1, if the branch is ready (we can decide what 'ready' means
later).
Diego.