From owner-svn-src-head@FreeBSD.ORG Fri May 10 10:21:45 2013 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BA95840F; Fri, 10 May 2013 10:21:45 +0000 (UTC) (envelope-from smckay@internode.on.net) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by mx1.freebsd.org (Postfix) with ESMTP id 70891F55; Fri, 10 May 2013 10:21:44 +0000 (UTC) Received: from vm-mail26.internode.on.net (HELO localhost) ([150.101.137.111]) by ipmail06.adl2.internode.on.net with ESMTP; 10 May 2013 19:51:43 +0930 MIME-Version: 1.0 X-Mailer: AtMail PHP 5.3 Message-ID: <65172.1368181303@internode.on.net> To: "Eitan Adler" , "Juli Mallett" Content-Type: text/plain; charset="utf-8" X-Origin: 144.131.35.110 X-Atmail-Account: smckay@internode.on.net Date: Fri, 10 May 2013 19:51:43 +0930 Subject: Re: svn commit: r250431 - head/usr.bin/xargs From: smckay@internode.on.net Content-Transfer-Encoding: quoted-printable Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: smckay@internode.on.net List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 May 2013 10:21:45 -0000 =20 =20 On Fri 10/05/13 17:50 , Juli Mallett jmallett@FreeBSD.org sent:=20 > Eitan,=20 >=20=20 > Are other changes coming to xargs for which these style changes make=20 > sense? If not, I'd say that style changes which only adjust vertical=20 > whitespace, especially those which mostly add vertical whitespace at=20 > the start of functions with no local variables (which is one of the=20 > most archaic and unusual things style(9) requires), are probably the=20 > most gratuitous and silly style changes to make. That doesn't even=20 > rise to being a style change, it's just a whitespace change. And I=20 > really do believe that vertical whitespace changes are much, much=20 > sillier than horizontal whitespace changes.=20 =20 Juli, it seems we're bothered by the same thing here: that at least=20 some of the vertical white space requirements of style(9) are=20 silly and (rightly) widely ignored. So I think we should change=20 the guide to fix this rather than damaging a lot of perfectly=20 readable code.=20 =20 I'd like to emphasise that I'm not even slightly cranky at Eitan for=20 his commit since we committers are presumed to have agreed to follow=20 style(9) and he's just changing code to match the official style. My=20 complaint is that the official style isn't useful in this small regard=20 and should be changed.=20 =20 > (Watch for standalone commits from people who used to be=20 > very active developers who have recently hit the threshold for getting=20 > commit bit reaper E-Mails. They're fairly instructive in the art of=20 > making occasional insignificant changes for the sake of making=20 > changes.)=20 =20 Well, I used to be a low activity developer and have transitioned to=20 being a very low activity developer, so I know the reaper and the=20 temptation of a quick fix to get it off your back. However it's better=20 to let the reaper pester you than to make a low quality commit. After=20 all, if you haven't anything new and interesting to add, there is always=20 that convenient list of bugs that could be fixed...=20 =20 Cheers,=20 =20 Stephen.=20