From bmah@employees.org  Tue Feb 25 09:05:15 2003
Return-Path: <bmah@employees.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F420D37B401; Tue, 25 Feb 2003 09:05:14 -0800 (PST)
Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6373343F75; Tue, 25 Feb 2003 09:05:13 -0800 (PST)
	(envelope-from bmah@employees.org)
Received: from bmah.dyndns.org (12-240-204-110.client.attbi.com[12.240.204.110])
          by sccrmhc03.attbi.com (sccrmhc03) with ESMTP
          id <2003022517051200300mrtjde>; Tue, 25 Feb 2003 17:05:12 +0000
Received: from intruder.bmah.org (localhost [127.0.0.1])
	by bmah.dyndns.org (8.12.7/8.12.6) with ESMTP id h1PH5Bst053960;
	Tue, 25 Feb 2003 09:05:11 -0800 (PST)
	(envelope-from bmah@intruder.bmah.org)
Received: (from bmah@localhost)
	by intruder.bmah.org (8.12.7/8.12.7/Submit) id h1PH5B5P053959;
	Tue, 25 Feb 2003 09:05:11 -0800 (PST)
Message-Id: <20030225170511.GA53886@intruder.bmah.org>
Date: Tue, 25 Feb 2003 09:05:11 -0800
From: "Bruce A. Mah" <bmah@freebsd.org>
To: oberman@es.net, bde@freebsd.org
Cc: freebsd-gnats-submit@freebsd.org
Subject: PR bin/33963

>Number:         48674
>Category:       bin
>Synopsis:       PR bin/33963
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 25 09:10:04 PST 2003
>Closed-Date:    Fri Feb 28 16:31:51 PST 2003
>Last-Modified:  Fri Feb 28 16:31:51 PST 2003
>Originator:     bmah@freebsd.org
>Release:        
>Organization:
>Environment:
>Description:
 --r5Pyd7+fXNt84Ff3
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 I'm trying to figure out what to do with this PR, which has been
 languishing for awhile and gives me momentary angst every week when it
 shows up in my PR reminders list.
 
 Some discussion with bde (shortly after the last PR followup) has made
 me realize that the root cause of these misleading sio(4) probe
 messages wasn't what I thought it was, and that I don't have the
 qualification or time ot deal with this.
 
 The alternatives seem to be:
 
 1.  Toss the PR back to freebsd-bugs.
 
 2.  Give it to bde, who's the de facto sio(4) maintainer.
 
 3.  Close it.
 
 Any thoughts?  Thanks.
 
 Bruce.
 
 --r5Pyd7+fXNt84Ff3
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.1 (FreeBSD)
 
 iD8DBQE+W6JG2MoxcVugUsMRAsl8AJ4j+2tpRz1fOhEjMWQkhl25CLeSqACeOZU7
 5wUjHIddn090HJ3mJucgQUI=
 =3WzO
 -----END PGP SIGNATURE-----
 
 --r5Pyd7+fXNt84Ff3--
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: ceri 
State-Changed-When: Fri Feb 28 16:31:09 PST 2003 
State-Changed-Why:  

Misfiled followup to bin/33963 [content migrated]. 


Responsible-Changed-From-To: gnats-admin->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Fri Feb 28 16:31:09 PST 2003 
Responsible-Changed-Why:  

Take from gnats-admin. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=48674 
>Unformatted:
