From owner-freebsd-current@FreeBSD.ORG Fri Oct 15 16:45:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 521B516A4CF for ; Fri, 15 Oct 2004 16:45:05 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D91F243D1D for ; Fri, 15 Oct 2004 16:45:04 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i9FGj3pU008421; Fri, 15 Oct 2004 12:45:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 15 Oct 2004 12:45:02 -0400 To: Mark Linimon , Robert Huff From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: network slowness/freez-up since update 10/11 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 16:45:05 -0000 At 1:17 PM -0500 10/14/04, Mark Linimon wrote: >On Thu, 14 Oct 2004, Robert Huff wrote: > >> Speaking only for myself: > > As someone who started tracking -CURRENT several months > > after the release of 5.0, and who has the proven ability to > > screw things up in ways unrelated to the actual code >:-( > >... filing a PR is (barring lack of sleep, low blood sugar, > > and/or "one of those days") the last resort not the first. > >(wearing bugmeister hat) > >I think the answer is "it depends". Certainly for build errors, >my understanding is that they shouldn't be PRs, under the theory >that someone will catch and fix them more quickly than the PR >database will catch up. > >But my assumption is that for pretty much everything else that >the PR database is the way to go. No? I think he's just saying that he doesn't like to file a PR until he's reasonably sure the problem is not some mistake on his side of things. Certainly I have had several times where I run into that. I start to write up a long and detailed PR for some problem, but in the process of gathering all the details I realize, "Oh, wait, this problem is because of those files I deleted last weekend, so I am picking up the wrong version of "... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu