Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com From: "Robert Collins" To: "'Conrad Scott'" , Subject: RE: System-wide mutexes and pthreads Date: Fri, 14 Jun 2002 00:33:13 +1000 Message-ID: <00a401c212e7$40e044a0$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 > 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. Ok. Hints. 0) Copy the scripts from winsup/maint to ~/bin and put it in your path. 1) ensure that the SHELL environment variable is set correctly. The scripts depend on this. 2) Use cvsmkpatch to make a patch. i.e. in the cygwin_daemon dir, run cvsmkpatch HEAD to get the current patch set. 3) use cvsmerge to update branch. i.e. cvsmerge HEAD. It'll ask you to resolve any conflicts before committing. 4) You'll probably want to run cvs update -kkvrcygwin_daemon ChangeLog after merges to ensure that the ChangeLog version stamp is correct. I will happily run regular merges for you, if you have -any- doubts. Rob