From owner-svn-src-head@freebsd.org  Tue Mar 20 15:29:12 2018
Return-Path: <owner-svn-src-head@freebsd.org>
Delivered-To: svn-src-head@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2AE88F56026
 for <svn-src-head@mailman.ysv.freebsd.org>;
 Tue, 20 Mar 2018 15:29:12 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from pmta2.delivery6.ore.mailhop.org
 (pmta2.delivery6.ore.mailhop.org [54.200.129.228])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id ACFC277B8F
 for <svn-src-head@freebsd.org>; Tue, 20 Mar 2018 15:29:11 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: 473cd9f9-2c53-11e8-b951-f99fef315fd9
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 67.177.211.60
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [67.177.211.60])
 by outbound2.ore.mailhop.org (Halon) with ESMTPSA
 id 473cd9f9-2c53-11e8-b951-f99fef315fd9;
 Tue, 20 Mar 2018 15:28:03 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2KFT2wT040201;
 Tue, 20 Mar 2018 09:29:02 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1521559742.99081.110.camel@freebsd.org>
Subject: Re: svn commit: r331226 - in head/sys: amd64/linux amd64/linux32
 i386/linux
From: Ian Lepore <ian@freebsd.org>
To: Bruce Evans <brde@optusnet.com.au>, Ed Maste <emaste@freebsd.org>
Cc: src-committers@freebsd.org, svn-src-all@freebsd.org,
 svn-src-head@freebsd.org
Date: Tue, 20 Mar 2018 09:29:02 -0600
In-Reply-To: <20180320183744.S950@besplex.bde.org>
References: <201803192126.w2JLQW0N039356@repo.freebsd.org>
 <20180320183744.S950@besplex.bde.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-src-head@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: SVN commit messages for the src tree for head/-current
 <svn-src-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-src-head>,
 <mailto:svn-src-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-src-head/>
List-Post: <mailto:svn-src-head@freebsd.org>
List-Help: <mailto:svn-src-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-src-head>,
 <mailto:svn-src-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 15:29:12 -0000

On Tue, 2018-03-20 at 19:19 +1100, Bruce Evans wrote:
> The random verb order is especially confsing for 'fix' and 'fixup'.
> 'fixup' is a noun, but is sometimes abused as a verb and adverb instead
> of the correct verb and adverb 'fix up'.  When it is placed at the
> end, e.g., for limit_fixup(), it is unclear if it is a noun or a verb.
> The noun form would mean a function returning a fixup and the verb
> form would mean a function fixing up something.  Using 'fix' instead
> of fix as a verb at the end is even worse since 'fix' really is both
> a noun and a verb.  The normal order in fixlimit makes it clear that
> it is used as a verb.

This stuff all becomes easier if you remember one simple rule:

    In English, there is no noun which cannot be verbed.

-- Ian