Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT syncretize DOT net>
To: "'Conrad Scott'" <Conrad DOT Scott AT dsl DOT pipex DOT com>,
   <cygwin-developers AT cygwin DOT com>
Subject: RE: System-wide mutexes and pthreads
Date: Thu, 13 Jun 2002 23:19:03 +1000
Message-ID: <009801c212dc$e3bbdc80$0200a8c0@lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <025a01c212db$80dcffa0$6132bc3e@BABEL>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000



> -----Original Message-----
> From: cygwin-developers-owner AT cygwin DOT com 
> [mailto:cygwin-developers-owner AT cygwin DOT com] On Behalf Of Conrad Scott
> Sent: Thursday, 13 June 2002 11:09 PM

> > Some pointers on creating branches would probably be good too.
> 
> I would certainly find some hints useful. For the moment, I'm 
> just carrying
> on hacking locally, but once there's a branch I'll re-factor 
> all the changes
> into reasonably small increments before submitting anything. 
> I hope that'll
> make it easier to review and trace.

I'll create a branch for you, that you can commit into. There is doco in
CVS on the scripts and how to use them though :} (src/winsup/maint).
 
> On the issue of review, how do we want to run this? Should I 
> submit patches
> for review and/or approval (to cygwin-patches)? or just go 
> ahead for the
> moment on the branch and wait for a larger approval 
> discussion at merge
> time? Or so happy medium between the two?

Submit patches for any bits you are 100% happy with - that won't need
further tweaking. Anything that you want design review on, discuss on
cygwin-developers, perhaps offering a proof-of-concept patch (i.e. via
cvsmkpatch) on cygwin-patches.
 
Rob