public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Jakub Wilk <jwilk@jwilk.net>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH 01/10] fanotify_init.2: tfix
Date: Sun, 21 Aug 2022 13:28:03 +0200	[thread overview]
Message-ID: <48974e65-dbd4-649b-2c21-c50fcfb7d734@gmail.com> (raw)
In-Reply-To: <20220821052837.tpxk3qe7vfwo7cef@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 3067 bytes --]

Hi Branden, Jakub,

On 8/21/22 07:28, G. Branden Robinson wrote:
> Hi Alex,
> 
> At 2022-08-20T01:28:04+0200, Alejandro Colomar wrote:
>>> -capability to create and intialize an fanotify group with limited functionality.
>>> +capability to create and initialize an fanotify group with limited functionality.
>>
>> should this be 'a fanotify' instead of 'an fanotify'?
> 
> Answering this requires people to document how the function/feature name
> is supposed to be pronounced.  Use "an" if what follows is a vowel
> sound.  Spelling is not a determining factor.
> 
> Unfortunately it is a tradition in Unix culture not to make
> pronouciation of its lexicon of (historically) hermetically terse
> identifier lexicon clear, so that the names of commands and functions
> that are well known enough to come up in conversation at conventions can
> be used a shibboleth to distinguish self-taught users and programmers
> (and clueless sales personnel and would-be entrepreneurs) from
> "authentic" Unix experts who underwent a proper apprenticeship, and
> through a chain of masters, can trace their tutelage to a luminary at
> the Bell Labs CSRC or UC Berkeley CSRG--someone with a name to be spoken
> in hushed tones like "Ritchie" or "Joy".
> 
> Does "troff" have one syllable or two?  Does one refer to the text
> editors as "ee-dee" and "vee-eye" or as if they were English diminutive
> names "Ed" and "Vi"?  One set of choices will mark you as a person who
> _might_ be worth conversing with; the other will get you a short look
> down a long nose and the cold shoulder.  We've got gates to keep.

You can guess the answers to those in my head ;)

> 
> Both Unix and the Linux kernel, the latter particularly in its
> development model, were levelling technologies.  They brought better OS
> technology and programming environments to much larger groups of people
> than had enjoyed them before.
> 
> But it is a sadly recurring theme of human history that as soon as some
> levelling process occurs, a certain type of person promptly moves in to
> restore a guild, caste, or other hierarchical social ordering that they
> are more comfortable with.
> 
> If you can't get an authoritative answer from a principal author of the
> fanotify API, I suggest reading the term as "eff-A-notify";

Ahh, makes sense now.  It hadn't occured to me that that was a possible 
pronounciation.  Anyway, it'll always be fa-notify in my head.  I'm 
waiting for sol-notify, which will be pronounced exactly as fanotify, 
but a tone higher :D

> this will
> then be implicitly documented by your choice of the article "an".

I was trying to come up with possible pronounciations that would have a 
vowel at the begining, but then I thought: no, who would pronounce this 
as f-a-notify?  It's too much work!  Heh!

>  It
> doesn't have anything to do with fans or the fourth degree of the major
> scale, after all.

Cheers,

Alex

P.S.: Patch applied.


-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-08-21 11:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 19:08 [PATCH 01/10] fanotify_init.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 02/10] landlock_restrict_self.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 03/10] memfd_secret.2: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 04/10] clockid_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 05/10] dev_t.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 06/10] itimerspec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 07/10] timespec.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 08/10] tm.3type: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 09/10] fanotify.7: tfix Jakub Wilk
2022-08-19 19:08 ` [PATCH 10/10] tcp.7: tfix Jakub Wilk
2022-08-19 23:28 ` [PATCH 01/10] fanotify_init.2: tfix Alejandro Colomar
2022-08-21  5:28   ` G. Branden Robinson
2022-08-21 11:28     ` Alejandro Colomar [this message]
2022-08-22 18:21   ` Jakub Wilk
2022-08-22 19:02     ` Alejandro Colomar
2022-08-19 23:32 ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48974e65-dbd4-649b-2c21-c50fcfb7d734@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox