From: Dominique Martinet <asmadeus@codewreck.org>
To: Tuomas Ahola <taahol@utu.fi>
Cc: v9fs@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation/fs/9p: fix broken link
Date: Sun, 23 Mar 2025 06:27:42 +0900 [thread overview]
Message-ID: <Z98rTkLrIq5wEw1a@codewreck.org> (raw)
In-Reply-To: <20250322153639.4917-1-taahol@utu.fi>
Tuomas Ahola wrote on Sat, Mar 22, 2025 at 05:36:39PM +0200:
> In b529c06f9dc7 (Update the documentation referencing Plan 9 from User
> Space., 2020-04-26), another instance of the link was left unfixed.
> Fix that as well.
Thank you, applied to 9p's -next
(sorry for double reply Tuomas, I had apparently missed the reply-all
key...)
> Signed-off-by: Tuomas Ahola <taahol@utu.fi>
> ---
> Documentation/filesystems/9p.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/filesystems/9p.rst b/Documentation/filesystems/9p.rst
> index 2bbf68b56b0d..28871200e87c 100644
> --- a/Documentation/filesystems/9p.rst
> +++ b/Documentation/filesystems/9p.rst
> @@ -40,7 +40,7 @@ For remote file server::
>
> mount -t 9p 10.10.1.2 /mnt/9
>
> -For Plan 9 From User Space applications (http://swtch.com/plan9)::
> +For Plan 9 From User Space applications (https://9fans.github.io/plan9port/)::
>
> mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
>
>
> base-commit: 88d324e69ea9f3ae1c1905ea75d717c08bdb8e15
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2025-03-22 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 15:36 [PATCH] Documentation/fs/9p: fix broken link Tuomas Ahola
2025-03-22 21:20 ` Dominique Martinet
2025-03-22 21:27 ` Dominique Martinet [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=Z98rTkLrIq5wEw1a@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=corbet@lwn.net \
--cc=ericvh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=taahol@utu.fi \
--cc=v9fs@lists.linux.dev \
/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).