This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: System-wide mutexes and pthreads
- 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>
- Date: Thu, 13 Jun 2002 23:19:03 +1000
- Subject: 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