From: Eric Blake <eblake@redhat.com>
To: nbd@other.debian.org
Cc: qemu-devel@nongnu.org
Subject: [PATCH] docs: Tweak location of qemu nbd extensions
Date: Fri, 2 Aug 2024 08:36:43 -0500 [thread overview]
Message-ID: <20240802133811.2001029-1-eblake@redhat.com> (raw)
Upstream QEMU is moving the location of its NBD docs, as of its commit
XXXX[1]. Instead of pointing to the raw git source file, point to the
rendered html version built from rST.
CC: qemu-devel@nongnu.org
Signed-off-by: Eric Blake <eblake@redhat.com>
---
[1] Commit id TBD, I will update this patch to match reality once
qemu's patch lands, and only push this once the new link actually
exists. See also
https://lists.gnu.org/archive/html/qemu-devel/2024-08/msg00223.html
---
doc/proto.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/proto.md b/doc/proto.md
index cf1f60f..565fbeb 100644
--- a/doc/proto.md
+++ b/doc/proto.md
@@ -963,7 +963,7 @@ Namespaces MUST be consist of one of the following:
Third-party implementations can register additional namespaces by
simple request to the mailing-list. The following additional
third-party namespaces are currently registered:
-* `qemu`, maintained by [qemu.org](https://gitlab.com/qemu-project/qemu/-/blob/master/docs/interop/nbd.txt)
+* `qemu`, maintained by [qemu.org](https://www.qemu.org/docs/master/interop/nbd.html)
Save in respect of the `base:` namespace described below, this specification
requires no specific semantics of metadata contexts, except that all the
--
2.45.2
next reply other threads:[~2024-08-02 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 13:36 Eric Blake [this message]
2024-08-03 13:18 ` [PATCH] docs: Tweak location of qemu nbd extensions Wouter Verhelst
2024-08-13 14:03 ` Eric Blake
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=20240802133811.2001029-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=nbd@other.debian.org \
--cc=qemu-devel@nongnu.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).