Date: Mon, 10 Aug 2020 19:42:23 -0400 From: Ed Maste <emaste@freebsd.org> To: =?UTF-8?Q?T=C4=B3l_Coosemans?= <tijl@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r363657 - head/crypto/openssh Message-ID: <CAPyFy2B_HSniv-Gji71HzA=CyDga_tATiyJHmjWaOvqrfkNr4g@mail.gmail.com> In-Reply-To: <20200729114322.4ff17fde@FreeBSD.org> References: <202007290034.06T0YOPQ044582@repo.freebsd.org> <20200729114322.4ff17fde@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 29 Jul 2020 at 05:43, T=C4=B3l Coosemans <tijl@freebsd.org> wrote: > > On Wed, 29 Jul 2020 00:34:24 +0000 (UTC) Ed Maste <emaste@FreeBSD.org> > wrote: > > I realise this is very pedantic, but my spell checker says it's > "block list", two words, so if you're using camel case it should > be UseBlockList. Indeed, I gave this some brief thought before committing, but decided to treat blocklist as a compound noun (as was blacklist). The name of the thing being enabled here is blocklist, using the blocklistd daemon. Also, Google shows me about 1.7M results for "blocklist" vs 2.5M for "block list" so it seems to be at least somewhat accepted as a single word / jargon in technical circles.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2B_HSniv-Gji71HzA=CyDga_tATiyJHmjWaOvqrfkNr4g>