From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11221 invoked by alias); 30 Apr 2004 05:00:02 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11066 invoked from network); 30 Apr 2004 05:00:00 -0000 Received: from unknown (HELO mta6.wss.scd.yahoo.com) (66.218.85.37) by sources.redhat.com with SMTP; 30 Apr 2004 05:00:00 -0000 Received: from specifixinc.com (24.7.123.142) by mta6.wss.scd.yahoo.com (7.0.016) (authenticated as jim@tuliptree.org) id 4072403F00D70D14; Thu, 29 Apr 2004 21:59:58 -0700 Message-ID: <4091DD6B.7020508@specifixinc.com> Date: Fri, 30 Apr 2004 09:47:00 -0000 From: Jim Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716 MIME-Version: 1.0 To: =?ISO-8859-2?Q?G=E1bor_L=F3ki?= CC: gcc@gcc.gnu.org Subject: Re: Branch for factoring? References: <4090EBF8.1010108@inf.u-szeged.hu> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2004-04/txt/msg01434.txt.bz2 Gábor Lóki wrote: > My question is, whether it is a good idea to start a development branch > for this work? How can it be arranged? Is there a need of cvs write > access? (Our copyright assignment has been filed). Yes, you must have cvs write access. Otherwise, there is no way for you to create a branch and add patches to it. Our policies for when it is OK to create branches are not well defined. Our docs just mention the mechanics, and don't mention policy at all. http://gcc.gnu.org/cvswrite.html#branches Branches can be useful if there is general interest in a patch, as it makes it easier for people at different places to collaberate. This seems to be primarily a U Szeged project, and there don't seem to be any collaberators outside U Szeged. Branches can be useful if the patches are large and invasive and need to be maintained for a long time, which does not seem to be the case with your patches at this time. There is also the issue of whether it is OK to give someone write access just so they can create a branch. I don't think this is good policy. I think someone should establish themselves as a regular contributor before they should consider making branches. I am speaking for myself here, and it is possible others will disagree. There are other solutions here. You can create your own CVS repository that mirrors the FSF one. You could maintain the work as patches. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com