From owner-cvs-all@FreeBSD.ORG Fri Oct 29 23:48:23 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B7A916A4CE; Fri, 29 Oct 2004 23:48:23 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2453243D41; Fri, 29 Oct 2004 23:48:23 +0000 (GMT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 177975D25E; Fri, 29 Oct 2004 16:48:23 -0700 (PDT) Date: Fri, 29 Oct 2004 16:48:23 -0700 From: Alfred Perlstein To: John Baldwin Message-ID: <20041029234823.GW24892@elvis.mu.org> References: <200410290824.i9T8Oflr047896@repoman.freebsd.org> <200410291338.50383.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410291338.50383.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_sig.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 23:48:23 -0000 * John Baldwin [041029 12:49] wrote: > On Friday 29 October 2004 04:24 am, Alfred Perlstein wrote: > > alfred 2004-10-29 08:24:41 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/kern kern_sig.c > > Log: > > Backout 1.291. > > > > re doesn't seem to think this fixes: > > Desired features for 5.3-RELEASE "More truss problems" > > Umm, the todo list always lags the fixes. This is nothing personal, it's just > that approving requests, etc. takes up most of re@'s limited time. Geez. > Usually the reson the todo gets updated is that someone explicitly e-mails > re@ saying "you can move this item from todo to done". As with other e-mails > sent to re@ (like MFC requests), if they don't respond to it, it probably got > lost in the bitbucket, so you have to resend it until you get an ack. (Kind > of like TCP. :-P) I made 3-4 requestss, each one had an ACK that said, "sorry, right on it!" It's just not acceptable. -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684