This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: System-wide mutexes and pthreads



> -----Original Message-----
> From: cygwin-developers-owner@cygwin.com 
> [mailto:cygwin-developers-owner@cygwin.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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]