From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15800 invoked by alias); 16 Jun 2009 11:13:49 -0000 Received: (qmail 15791 invoked by uid 22791); 16 Jun 2009 11:13:48 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_21 X-Spam-Check-By: sourceware.org Received: from smtp-116-tuesday.nerim.net (HELO maiev.nerim.net) (62.4.16.116) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Jun 2009 11:13:40 +0000 Received: from hector.lesours (ours.starynkevitch.net [213.41.244.95]) by maiev.nerim.net (Postfix) with ESMTP id 8FD73B8312 for ; Tue, 16 Jun 2009 13:13:37 +0200 (CEST) Received: from glinka.lesours ([192.168.0.1]) by hector.lesours with esmtp (Exim 4.69) (envelope-from ) id 1MGWbh-00076q-KG for gcc@gcc.gnu.org; Tue, 16 Jun 2009 13:13:37 +0200 Message-ID: <4A377E77.3010807@starynkevitch.net> Date: Tue, 16 Jun 2009 11:13:00 -0000 From: Basile STARYNKEVITCH User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: GCC Mailing List Subject: Re: "plugin"-ifying the MELT branch. References: <4A281366.9010004@starynkevitch.net> In-Reply-To: <4A281366.9010004@starynkevitch.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-06/txt/msg00341.txt.bz2 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 create a new melt-plugin-branch in a few hours (or days), unless there is some objections to it;I will progressively move code from the current MELT branch melt-branch into this melt-plugin-branch to make MELT a big plugin. Also, does such a thing should be called a branch. After all, it is not a derivative of an existing trunk! Maybe it should be called something different! This also brings interesting questions: how should plugins in general be structured? Do they need some autoconf hackery? My goal is of course to make MELT a big (meta) plugin suitable to work with the standard trunk (ie future 4.5). Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basilestarynkevitchnet mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} ***