From owner-cvs-src@FreeBSD.ORG Fri Apr 18 13:07:07 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8196537B407 for ; Fri, 18 Apr 2003 13:07:07 -0700 (PDT) Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BCD443FE3 for ; Fri, 18 Apr 2003 13:07:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28006 invoked from network); 18 Apr 2003 20:07:11 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 18 Apr 2003 20:07:11 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h3IK72Ov079300; Fri, 18 Apr 2003 16:07:02 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200304181851.h3IIpqB9021674@repoman.freebsd.org> Date: Fri, 18 Apr 2003 16:07:04 -0400 (EDT) From: John Baldwin To: Julian Elischer cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: RE: cvs commit: src/sys/sys proc.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2003 20:07:07 -0000 On 18-Apr-2003 Julian Elischer wrote: > julian 2003/04/18 11:51:52 PDT > > FreeBSD src repository > > Modified files: > sys/sys proc.h > Log: > Revert parts of 1.309 to allow processes to have a signal mask > independently from the threads again. > Will be adding code to use this soon.. *sigh* I guess I need to just throw away my 100k of diffs to cleanup proc locking. Can you and Jeff please sit down and develop a plan for what you both need for signals instead of just committing patches back and forth? Jeff at least has offered to rework signals if you will provide him with your interface requirements. I realize that may be a bit one-sided, so I don't really care who implements it, but I would like to see both of you sit down and come up with an interface w/o assuming a certain implementation first and once you have that in place then design an implementation that implements all the requirements. Please. People keep asking for proc locking but it can't be delivered if the code changes every week. BTW, perhaps you and Jeff have already done all this in which case a 'Reviewed by' would have been _greatly_ appreciated. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/