From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] exportfs: fix debug logging
Date: Mon, 16 Aug 2021 12:56:27 -0500 [thread overview]
Message-ID: <20210816125627.5c9aec76@spruce.localdomain> (raw)
In-Reply-To: <1FB5D1B9C97EB96BD9B642CB8AD1362D@qak>
On Sun, 15 Aug 2021 18:29:16 +0200
kvik@a-b.xyz wrote:
> This is a nice simplification. Perhaps you could take a chance to
> rename the -d flag to -D for consistency with most other file servers.
Let's move renaming -d to -D for another patch. Then we can do it all
at once. In the meantime, I would like my patch committed (please).
On Mon, 16 Aug 2021 15:55:10 +0200
kvik@a-b.xyz wrote:
> I do realize now that exportfs mixes the 9p trace and general debug
> output, so maybe -d is more appropriate after all.
My conception is that -d and -D do the same thing, which is whitebox
debugging both the program's actions and its communications that
trigger those actions.
On Mon, 16 Aug 2021 01:20:39 -0400
ori@eigenstate.org wrote:
> Yeah. it's just a convention (though
> I often wish that we'd taken a more
> out of the way character for this,
> like -δ. :/)
I support this notion, but I don't have any concrete examples of
mnemonics that would be better suited for -d than "debug" or
"directory". -D is simple enough to free -d for more common tasks.
(Alternatively, debug could be a compile flag, but we chose convenience
over needing to recompile.)
Thanks,
Amavect
next prev parent reply other threads:[~2021-08-17 2:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 1:11 Amavect
2021-08-13 5:16 ` [9front] " Amavect
2021-08-13 19:11 ` [9front] " ori
2021-08-14 22:04 ` Amavect
2021-08-15 16:29 ` kvik
2021-08-16 4:40 ` unobe
2021-08-16 5:20 ` ori
2021-08-16 16:49 ` unobe
2021-08-16 13:55 ` kvik
2021-08-16 16:50 ` unobe
2021-08-16 17:56 ` Amavect [this message]
2021-08-16 19:32 ` ori
2021-08-16 22:48 ` ori
2021-08-18 14:24 ` cinap_lenrek
2021-08-18 14:49 ` k m
2021-08-16 20:19 ` Steve Simon
2021-08-16 23:26 ` ori
2021-08-13 6:46 unobe
2021-08-13 11:15 ` Amavect
2021-08-14 20:14 ` Stuart Morrow
2021-08-15 16:40 ` kvik
2021-08-15 20:44 ` Stuart Morrow
2021-08-16 20:17 ` Humm
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=20210816125627.5c9aec76@spruce.localdomain \
--to=amavect@gmail.com \
--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).