From owner-freebsd-bugs Sun May 3 09:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19921 for freebsd-bugs-outgoing; Sun, 3 May 1998 09:54:19 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19914 for ; Sun, 3 May 1998 09:54:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA11662; Sun, 3 May 1998 18:53:44 +0200 (CEST) To: Randall Hopper cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5296 In-reply-to: Your message of "Sun, 03 May 1998 12:35:20 EDT." <19980503123520.A5017@ct.picker.com> Date: Sun, 03 May 1998 18:53:43 +0200 Message-ID: <11660.894214423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980503123520.A5017@ct.picker.com>, Randall Hopper writes: >Ok, now I know. In the future I'll be less intent on investigating and >logging detailed PRs for bugs in less trafficed areas since they could just >be closed. This is the wrong response. The right response would have been: "Ok, now I know. In the future I will try to provide a patch for the problems I find, since nobody would expect people who spend their spare-time on a free OS to be able to fix all the bugs by them selves." >This is different from the style of bug tracking I'm used to. This is different from most other software you use. >This open PR state info is useful for record keeping and searches. Unfortunately, it also clutters up the view and prevents more severe problems from getting the attention the need. >Or if someone is looking for an area to contribute that'll make >the biggest difference, they might like to see how many PRs are outstanding >on the candidate enditems. I could have judge this PR wrong, but any PR which I think a committer would be able to make a meal out of gets put in the "suspended" state which means "Come and get it guys". > |Why don't you take a stab at fixing it yourself ? If you send us a patch > |bugs like this are likely to get fixed. > >If it bubbles to the top of my priority, I will. As a workaround, I just >ignore the PID file since it's existance can't be counted on so this isn't >too high a priority. Exactly. And SLIP is on the way out loosing ground to PPP rapidly, so I don't think anybody would ever assign sufficient priority to this problem, and consequently: I closed it. It is a matter of keeping the tabletop if not even clean or tidy, then at least stable in a gravitational field... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message