From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Jeff Cody" <codyprime@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Mark VHDX block driver as "Odd Fixes"
Date: Thu, 2 Oct 2025 16:23:41 +0200 [thread overview]
Message-ID: <1f77cfe8-08fb-477a-89b0-e885d57df776@linaro.org> (raw)
In-Reply-To: <20251002125446.2500179-1-peter.maydell@linaro.org>
On 2/10/25 14:54, Peter Maydell wrote:
> In 2018 (in commit 5f5246b6b) Jeff Cody stepped down as block
> maintainer, but left himself as maintainer for VHDX and with a status
> of "Supported", with the rationale:
>
> For VHDX, added my personal email address as a maintainer, as I can
> answer questions or send the occassional bug fix. Leaving it as
> 'Supported', instead of 'Odd Fixes', because I think the rest of the
> block layer maintainers and developers will upkeep it as well, if
> needed.
>
> However, today the way we treat subsystems which are only maintained
> under the general umbrella of a wider system is usually to mark them
> as "Odd Fixes". The vhdx.c code has had no commits which aren't a
> part of more general refactoring changes since 2020, and Jeff himself
> hasn't been active on qemu-devel since 2018, so this seems also to be
> how we've handled the code in practice.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> (Jeff, I've left your email in under the M: line, but we could remove
> it if you'd prefer.)
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-10-02 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 12:54 [PATCH] MAINTAINERS: Mark VHDX block driver as "Odd Fixes" Peter Maydell
2025-10-02 14:23 ` Philippe Mathieu-Daudé [this message]
2025-10-23 13:20 ` Peter Maydell
2025-10-24 11:19 ` Kevin Wolf
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=1f77cfe8-08fb-477a-89b0-e885d57df776@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=codyprime@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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).