From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Add cli and ioctl to deregister devices
Date: Fri, 8 Dec 2017 02:17:57 +0000 (UTC) [thread overview]
Message-ID: <pan$e67bd$548c1a2e$2d7222f9$63f69c71@cox.net> (raw)
In-Reply-To: 2eb9cb20-e972-f642-d116-2d7dc4417fe8@oracle.com
Anand Jain posted on Fri, 08 Dec 2017 08:51:43 +0800 as excerpted:
> On 12/07/2017 10:52 PM, Austin S. Hemmelgarn wrote:
>> On 2017-12-07 09:36, Anand Jain wrote:
>>> Add ability to deregister a or all devices. I have named this sub cmd
>>> as deregister, but I am open to your suggestions.
>> Being a bit picky here, but from the perspective of a native speaker of
>> American English, I would say that 'deregister' sounds rather synthetic
>> and somewhat harsh and alien.
>>
>> Given that, as odd as it sounds, I think 'ignore' might be a more user
>> friendly name for the sub-command. It accurately describes what the
>> command is doing (telling the kernel to ignore the device), and it's a
>> lot less alien sounding than 'deregister'.
>>
>> If you're set on having it be based on the word 'register', I would
>> suggest changing it to 'unregister', as I think that sounds more
>> natural than 'deregister'.
>>
>> Additionally, if you do continue with 'deregister' or go with
>> 'unregister' as the name though, I would suggest adding 'register' as a
>> synonym for the 'scan' sub-command to keep things reasonably
>> symmetrical.
>
> A look up on unregister lead me to use deregister as more appropriate.
> Anyway I won't bother much, I will be go be suggestions, and how about
> unscan, since scan is already there. OR how about purge.
This is a bikeshed I think I have a beautiful color suggestion for! =:^)
Seriously, the normal purpose of scanning is to record particular details
of what was seen during the scan, based on some desired scanning criteria.
So what do you call it when you need to "forget" the information you
scanned for?
What about simply "forget", btrfs device forget ? That sounds the most
natural to me, certainly far more so than the apparently freshly created
word "unscan", tho that would certainly deliver the meaning.
And FWIW, "deregister", just.. no. (I too would vote unregister if we're
sticking with the register root-word, but I have a feeling that may be a
regional/en-US preference and some other English regional variants may
find deregister is the less terrible to their ear. That may explain
whatever commentary under unregister led you to go with deregister.)
"Deregister" sounds like something a computer programmer might say to
describe the process, but I can't imagine a "normal" person using the
word, except possibly in the context of removing someone from the voter
rolls (where one "registers" to vote, so "deregister" could be a a
reasonably natural term for reversing that) or the like.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-12-08 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 14:36 [PATCH v5 0/3] Add cli and ioctl to deregister devices Anand Jain
2017-12-07 14:36 ` [PATCH v5 1/3] btrfs: add function to device list delete Anand Jain
2017-12-07 14:36 ` [PATCH v5 2/3] btrfs: introduce feature to deregister a btrfs device Anand Jain
2017-12-07 14:36 ` [PATCH v5 3/3] btrfs: add feature to deregister all unmounted devices Anand Jain
2017-12-07 14:52 ` [PATCH v5 0/3] Add cli and ioctl to deregister devices Austin S. Hemmelgarn
2017-12-08 0:51 ` Anand Jain
2017-12-08 2:17 ` Duncan [this message]
2017-12-08 13:09 ` Austin S. Hemmelgarn
2017-12-12 7:37 ` Anand Jain
2017-12-07 14:52 ` [PATCH v5 1/2] btrfs-progs: add cli to deregister a device Anand Jain
2017-12-07 14:52 ` [PATCH v5 2/2] btrfs-progs: add feature to deregister all devices Anand Jain
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='pan$e67bd$548c1a2e$2d7222f9$63f69c71@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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