From owner-freebsd-current@FreeBSD.ORG Wed Aug 18 18:27:17 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B591A10656A4; Wed, 18 Aug 2010 18:27:17 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7851F8FC13; Wed, 18 Aug 2010 18:27:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o7IIGYqj084323; Wed, 18 Aug 2010 12:16:34 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 18 Aug 2010 12:16:35 -0600 (MDT) Message-Id: <20100818.121635.431102609571763034.imp@bsdimp.com> To: gabor@freebsd.org From: "M. Warner Losh" In-Reply-To: <4C6C1CFE.6060900@FreeBSD.org> References: <4C6505A4.9060203@FreeBSD.org> <4C6C1CFE.6060900@FreeBSD.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: dimitry@andric.com, dougb@freebsd.org, delphij@freebsd.org, current@freebsd.org Subject: Re: Official request: Please make GNU grep the default X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 18 Aug 2010 18:27:17 -0000 In message: <4C6C1CFE.6060900@FreeBSD.org> Gabor Kovesdan writes: : When reply, please remove core@ from CC, let's not bother them with : this, I just wanted to let them know that I'm not neglecting this : issue but if still demanded for a good reason, I'll switch back to : default GNU grep. So making it default turned out well in the end. Sure, there was pain involved (but this is current), but making it default exposed the pain that would otherwise have gone unnoticed. The big hue and cry, while excessive at times, did result in people actually running the profiling tools which pointed to the buffering as the number one thing to fix. That being fixed now, it looks like we can go to the next stage: benchmarking again. Thanks, Gabor and everybody else that contributed, for seeing this through. Warner