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'" Cc: Subject: RE: System-wide mutexes and pthreads Date: Sat, 15 Jun 2002 21:32:26 +1000 Message-ID: <002201c21460$5359df90$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 In-Reply-To: <07c501c2132d$f4868d70$6132bc3e@BABEL> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > -----Original Message----- > From: Conrad Scott [mailto:Conrad DOT Scott AT dsl DOT pipex DOT com] > Sent: Friday, 14 June 2002 8:59 AM > > Submit patches for any bits you are 100% happy with - that > won't need > > further tweaking. > > I'm not sure whether you mean "submit" or "commit" here? If you mean > "submit", it doesn't seem that I've much need for CVS write > access at all. Here's the process: A) hack on the branch B) Decide that feature foo is ready for release (i.e. won't destabilise HEAD, and is not going to change in such a fashion as to break ABI in the future. C) Submit a patch, based on the HEAD->branch delta, to implement foo in HEAD, whilst leaving all alpha and beta code in the branch. > Also, to check the interpretation of "100% happy": those cygserver/shm > patches I sent earlier this week, what category would they > fall into? Most would be 100% happy IMO. The debug consolidation one, I've got some longer term ideas as discussed, but is probably 100% ok as well. > My > feeling is that they don't add new features or change anything of the > fundamental design, they could be committed directly. Or am I > out of line > here? Nope. Just fine. Rob