From: Stefan Hajnoczi <stefanha@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/4] NBD patches through 2025-03-05
Date: Fri, 7 Mar 2025 15:18:19 +0800 [thread overview]
Message-ID: <20250307071819.GA362024@fedora> (raw)
In-Reply-To: <20250305230542.2225013-6-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.0 for any user-visible changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-03-07 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 23:05 [PULL 0/4] NBD patches through 2025-03-05 Eric Blake
2025-03-05 23:05 ` [PULL 1/4] iotest: Unbreak 302 with python 3.13 Eric Blake
2025-03-05 23:05 ` [PULL 2/4] iotests: Stop NBD server in test 162 before starting the next one Eric Blake
2025-03-05 23:05 ` [PULL 3/4] qapi: merge common parts of NbdServerOptions and nbd-server-start data Eric Blake
2025-03-05 23:05 ` [PULL 4/4] nbd: Defer trace init until after daemonization Eric Blake
2025-03-07 7:18 ` Stefan Hajnoczi [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=20250307071819.GA362024@fedora \
--to=stefanha@redhat.com \
--cc=eblake@redhat.com \
--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).