From: fgergo@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] spec in plan9port?
Date: Tue, 6 Sep 2022 16:32:53 +0200 [thread overview]
Message-ID: <CA+ctqrp9q_9m+1VZh9NBeRD=XMmC+AWEuBHtTCEuN9-NZX0i2Q@mail.gmail.com> (raw)
In-Reply-To: <96ABDEC487079A9897311DE37A200542@eigenstate.org>
On 9/6/22, ori@eigenstate.org <ori@eigenstate.org> wrote:
> Quoth fgergo@gmail.com:
>> Sure, thanks for clarifying! Where else is or could be the passing of
>> spec to Tattach implemented?
>
> mount, or whatever is doing the mounting.
Hence my original question.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d821c657f5e5431-M0b01ba540264412ffb4049de
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-09-06 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 12:05 fgergo
2022-09-05 19:54 ` ori
2022-09-06 7:26 ` fgergo
2022-09-06 13:08 ` ori
2022-09-06 14:32 ` fgergo [this message]
2022-09-06 14:41 ` ori
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='CA+ctqrp9q_9m+1VZh9NBeRD=XMmC+AWEuBHtTCEuN9-NZX0i2Q@mail.gmail.com' \
--to=fgergo@gmail.com \
--cc=9fans@9fans.net \
/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).