From: Markus Armbruster <armbru@redhat.com>
To: Kamay Xutax <admin@xutaxkamay.com>
Cc: qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH RFC v1 0/1] clipboard sharing implementation for SDL
Date: Thu, 09 Nov 2023 08:01:00 +0100 [thread overview]
Message-ID: <87pm0j76mr.fsf@pond.sub.org> (raw)
In-Reply-To: <20231108022139.12503-1-admin@xutaxkamay.com> (Kamay Xutax's message of "Wed, 8 Nov 2023 03:21:38 +0100")
Kamay Xutax <admin@xutaxkamay.com> writes:
> Hello,
>
> This is my first try contributing to QEMU,
Welcome!
> and I would like some advices before merging my patch into master branch.
First piece of advice: it's a busy mailing list, and to get people's
attention, cc: them. For a patch, you want to cc: maintainers of the
code you patch. To find them, use scripts/get_maintainer.pl and
exercise judgement. Let me show you:
$ scripts/get_maintainer.pl ./0001-*patch
Gerd Hoffmann <kraxel@redhat.com> (odd fixer:Graphics)
"Marc-André Lureau" <marcandre.lureau@redhat.com> (odd fixer:Graphics)
Paolo Bonzini <pbonzini@redhat.com> (maintainer:Meson)
"Daniel P. Berrangé" <berrange@redhat.com> (reviewer:Meson)
Thomas Huth <thuth@redhat.com> (reviewer:Meson)
"Philippe Mathieu-Daudé" <philmd@linaro.org> (reviewer:Meson)
qemu-devel@nongnu.org (open list:All patches CC here)
Since the patch's Meson part is straightforward, I'd just cc: the two
Graphics people, I'm doing it in this message, so you don't have to.
[...]
prev parent reply other threads:[~2023-11-09 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 2:21 [PATCH RFC v1 0/1] clipboard sharing implementation for SDL Kamay Xutax
2023-11-08 2:21 ` [PATCH RFC v1 1/1] ui/sdl2: " Kamay Xutax
2023-11-14 11:23 ` Marc-André Lureau
2023-11-14 12:28 ` BALATON Zoltan
2023-11-14 12:36 ` Marc-André Lureau
2023-11-09 7:01 ` Markus Armbruster [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=87pm0j76mr.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=admin@xutaxkamay.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@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).