From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org, Jacob Moody <moody@mail.posixcafe.org>
Subject: Re: [9front] [PATCH] Unmount to remove sharp devices.
Date: Thu, 26 May 2022 22:25:36 -0400 [thread overview]
Message-ID: <5b0acec2-1dc4-1374-9bdc-6596f447f679@fjrhome.net> (raw)
In-Reply-To: <b5153f1b1c276e0c@orthanc.ca>
I believe the entire point is that you can only remove - not add. There
is only one operation.
The "prefixes" are to make it more convenient to specify the set of
devices being masked, not to change what is being done to them.
On 5/26/22 9:11 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> Instead of dancing around all these prefixes, why not just be
> explicit about it. There are three cases:
>
> chdev add abcd # add 'abcd' to the current set
> chdev del abcd # remove 'abcd' from the current set
> chdev abcd # 'abcd' becomes the absolute set
>
> No ambiguities, and dead simple to parse.
>
prev parent reply other threads:[~2022-05-27 2:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 14:09 Jacob Moody
2022-05-04 15:05 ` ori
2022-05-04 15:31 ` ori
2022-05-04 16:15 ` Stanley Lieber
2022-05-04 17:41 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-04 17:55 ` Jacob Moody
2022-05-05 1:59 ` Alex Musolino
2022-05-05 16:07 ` Jacob Moody
2022-05-08 2:55 ` Jacob Moody
2022-05-11 14:47 ` Jacob Moody
2022-05-11 16:11 ` Stanley Lieber
2022-05-12 4:29 ` Jacob Moody
2022-05-12 3:18 ` ori
2022-05-12 5:10 ` Jacob Moody
2022-05-12 14:21 ` ori
2022-05-23 5:42 ` Jacob Moody
2022-05-23 17:06 ` cinap_lenrek
2022-05-23 17:37 ` Jacob Moody
2022-05-25 19:03 ` Jacob Moody
2022-05-25 20:53 ` hiro
2022-05-25 21:20 ` Jacob Moody
2022-05-26 5:55 ` Jacob Moody
2022-05-26 23:36 ` unobe
2022-05-27 0:33 ` Jacob Moody
2022-05-27 3:25 ` unobe
2022-05-26 3:13 ` ori
2022-05-27 1:11 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-27 2:25 ` Frank D. Engel, Jr. [this message]
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=5b0acec2-1dc4-1374-9bdc-6596f447f679@fjrhome.net \
--to=fde101@fjrhome.net \
--cc=9front@9front.org \
--cc=moody@mail.posixcafe.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;
as well as URLs for NNTP newsgroup(s).