From: Wouter Verhelst <w@uter.be>
To: Eric Blake <eblake@redhat.com>
Cc: nbd@other.debian.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] docs: Tweak location of qemu nbd extensions
Date: Sat, 3 Aug 2024 15:18:35 +0200 [thread overview]
Message-ID: <Zq4uK9Z6GX7Ga-qY@pc220518.home.grep.be> (raw)
In-Reply-To: <20240802133811.2001029-1-eblake@redhat.com>
On Fri, Aug 02, 2024 at 08:36:43AM -0500, Eric Blake wrote:
> 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.
ACK. Please push as soon as that lands.
--
w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}
I will have a Tin-Actinium-Potassium mixture, thanks.
next prev parent reply other threads:[~2024-08-03 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 13:36 [PATCH] docs: Tweak location of qemu nbd extensions Eric Blake
2024-08-03 13:18 ` Wouter Verhelst [this message]
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=Zq4uK9Z6GX7Ga-qY@pc220518.home.grep.be \
--to=w@uter.be \
--cc=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).