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
Message-ID: <037b01c148cb$2c51bdc0$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: winsup/maint 
Date: Sat, 29 Sep 2001 19:43:18 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 29 Sep 2001 09:50:41.0510 (UTC) FILETIME=[33594060:01C148CC]

Ok, I've put the cvs scripts for branch development in there. I need to
update them soon to include Henrik Nordstrom's copyright - he's
explicitly put them in the public domain following my query to him about
licencing. (They are trivial in length :]).

The rules.txt and projects.txt file in the ChangeLog I managed to forget
to CVS add :]. I'll rectify that shortly. The rules are adapted from
squid devel tree rules - I expect that there may be differences of
opinion here - I'm not trying to set these rules, just to have _whatever
they are here_ written down. With branch based develop this is fairly
important.

The projects.txt file is just a list of the branches and what they are
for. It should really be maintained outside the winsup cvs tree, to
ensure that it doesn't accidentally get modified on a non-HEAD branch
(as it's meta data, it shouldn't get modified except on HEAD). If space
on the website can be made for it, then we can hyperlink to the CVS web
pages for the branch with the correct tag, and other niceties like live
diffs (via another script :]) and auto created patches :}. But those
things are not for us so much, as for bleeding edge testers wanting to
help us via feedback and the like.

Rob