From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] plumber: remove $plumbsrv, add optional srvname, usage check
Date: Thu, 09 Sep 2021 17:21:32 +0200 [thread overview]
Message-ID: <DF56C1D1686EBB0EE1834795CC36C186@qak> (raw)
In-Reply-To: <CAECFF9BC8BB3EAFBC0D8F96C64E4F28@wopr.sciops.net>
> Quoth qwx@sciops.net:
The mount point on the other hand is always /mnt/plumb.
Wow, I'm drunk and dumb and stupid. Yes, of course the -m flag
alone doesn't change anything.
The option I implied is only posting the srv file when requested
whence you wouldn't need to clean it up afterwards in the usual
case.
Sorry for confusion.
next prev parent reply other threads:[~2021-09-09 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 17:46 qwx
2021-09-07 22:06 ` umbraticus
2021-09-08 8:51 ` sirjofri
2021-09-08 14:18 ` ori
2021-09-08 14:29 ` kvik
2021-09-08 17:35 ` qwx
2021-09-09 15:07 ` kvik
2021-09-09 15:21 ` kvik [this message]
2021-09-09 18:05 ` qwx
2021-09-09 18:16 ` qwx
2021-09-10 21:05 ` qwx
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=DF56C1D1686EBB0EE1834795CC36C186@qak \
--to=kvik@a-b.xyz \
--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).