From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Unmount to remove sharp devices.
Date: Wed, 25 May 2022 15:20:23 -0600 [thread overview]
Message-ID: <f1dfd9ef-faf2-6661-f58e-91e4b4b6f8ed@posixcafe.org> (raw)
In-Reply-To: <CAFSF3XO+ppp+GVTU0d1g_GWLFNXLqCyK1R0Eju6+eV-V0TX15Q@mail.gmail.com>
On 5/25/22 14:53, hiro wrote:
> hating those runes.
Fair enough, I'll toss them.
> did you consider: chdev REGEXP
> could be the expanded version that allows driverA|driverB|driver[CDE]
> could also allow ! or -v for reversing the meaning.
I have a mild preference to keep it just a string of characters, but
I could be convinced otherwise. I like that the characters provided
match how they are accessed like '#A'. The drivers do keep their
actual full name stored on the struct, so all the context is there.
Might make 'chdev' lines in namespace files a bit less opaque.
> alternatively, why not use 0 instead of ∅ and '!' instead of ∉ ?
I like this. My only gripe is wanting some sort of implicit prefix
replacement for ∈. But I can get over that.
next prev parent reply other threads:[~2022-05-25 21:23 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 [this message]
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.
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=f1dfd9ef-faf2-6661-f58e-91e4b4b6f8ed@posixcafe.org \
--to=moody@mail.posixcafe.org \
--cc=9front@9front.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).