Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Mon, 24 Sep 2001 18:36:59 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: CVS branches RFC
Message-ID: <20010924183659.B32477@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <0db601c144fe$3ec53ca0$0200a8c0 AT lifelesswks> <20010924170130 DOT B31556 AT redhat DOT com> <0f5701c14546$0bd99280$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0f5701c14546$0bd99280$0200a8c0@lifelesswks>
User-Agent: Mutt/1.3.21i

On Tue, Sep 25, 2001 at 08:12:48AM +1000, Robert Collins wrote:
>
>----- Original Message -----
>From: "Christopher Faylor" <cgf AT redhat DOT com>
>To: <cygwin-developers AT cygwin DOT com>
>Sent: Tuesday, September 25, 2001 7:01 AM
>Subject: Re: CVS branches RFC
>
>
>> On Mon, Sep 24, 2001 at 11:38:49PM +1000, Robert Collins wrote:
>> >The thoughts here are derived from my experience with squid
>> >development...
>> >
>> >I find that being able to create numerous small cvs branches for
>> >specific development tasks has made a significant difference to the
>> >squid development rate. Pretty much _everything_ that is new or
>> >non-trivial is developed on a branch first, and then brought into
>HEAD.
>>
>> This is a fine idea.  Please feel free to develop on branches.
>
>Thank you, I will :]. Would you like me to convert over the doco about
>the scripts and how to use them, for cygwin developers to refer to?
>
>Also, I just want to confirm that there is no issue with creating the
>tags at the src level (given the number of projects in the src module
>I'm a leetle nervous) - so that winsup and newlib are both caught. The
>script creates two branchs for each working branch - one by the branch
>name (ie cygwin_daemon) and another to track the difference between HEAD
>and cygwin_daemon - Z_cygwin_daemon_merge_HEAD. This allows diff
>creation, without respect to the current state of HEAD. I.e. HEAD
>development does not invalidate the branch state.

If people think that scripts are a good idea, that's fine with me.

I don't think that I really have the authority to allow people to
create branches in newlib.  Maybe we should get permission from
newlib AT sources DOT redhat DOT com before creating branches there.

Should we create another directory in winsup for dealing with
these kind of things like "winsup/scripts" or "winsup/maint"?

cgf