From owner-svn-src-all@FreeBSD.ORG Thu Jul 1 09:15:03 2010 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 648881065673 for ; Thu, 1 Jul 2010 09:15:03 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 010CF8FC25 for ; Thu, 1 Jul 2010 09:15:02 +0000 (UTC) Received: (qmail 9233 invoked by uid 399); 1 Jul 2010 09:15:00 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 1 Jul 2010 09:15:00 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Thu, 1 Jul 2010 02:14:41 -0700 (PDT) From: Doug Barton To: Jack Vogel In-Reply-To: Message-ID: References: <201007010503.o6153O78066276@svn.freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: svn-src-head@freebsd.org, Kevin Lo , svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r209622 - head/sys/dev/ixgbe X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 09:15:03 -0000 On Wed, 30 Jun 2010, Jack Vogel wrote: > I went to a LOT of trouble setting up a mirror at home and just as I > went to commit the change its updated. Not sure if you mean "mirror" literally here or not. I assume that you mean "local tree checked out from the master svn server." In any case, I'm sure that we all appreciate your efforts, and the timing of the various commits was was unfortunate. In situations like this it's usually a good idea to both double check the sources, as well as the svn mailing list to see if someone has already gotten around to fixing it. > While I understand the good intentions, please don't do this again. If > I had been unresponsive for days or something I understand, but its > been hours, and I was fixing it. I can certainly understand your frustration here, so I'm going to (once again) assume (and you know what they say about that ...) that you didn't mean "days" literally since clearly it would not be Ok to have the build broken (and tinderbox error messages, etc.) for days. In situations like this what's generally done is to respond to a relevant tinderbox message to the effect of "I see the problem, I'm working on the fix, and it should be done by $TIME." That way people know you're on the case and can let you do your thing in peace. Of course, the gold standard is to test changes before committing them, but it's not at all uncommon to have test builds complete successfully under your normal working conditions but fail in the tinderbox. It even happened to me once ... hth, Doug (Ok, maybe more than once) -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso