From: Markus Armbruster <armbru@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Carwyn Ellis" <carwynellis@gmail.com>,
qemu-devel@nongnu.org, "BALATON Zoltan" <balaton@eik.bme.hu>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH 0/2] qemu-options: Improve -display cocoa documentation
Date: Mon, 18 Dec 2023 07:14:17 +0100 [thread overview]
Message-ID: <877clcujeu.fsf@pond.sub.org> (raw)
In-Reply-To: <20231214-options-v1-0-113f347b0e3f@daynix.com> (Akihiko Odaki's message of "Thu, 14 Dec 2023 15:31:34 +0900")
Could this go via qemu-trivial?
Akihiko Odaki <akihiko.odaki@daynix.com> writes:
> For the context, see:
> https://lore.kernel.org/all/e3839467-6d4c-e8e6-9247-a71fafe5505e@eik.bme.hu/
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> Akihiko Odaki (2):
> qemu-options: Unify the help entries for cocoa
> qemu-options: Tell more for -display cocoa
>
> qemu-options.hx | 21 ++++++++++++++++++---
> 1 file changed, 18 insertions(+), 3 deletions(-)
> ---
> base-commit: 4705fc0c8511d073bee4751c3c974aab2b10a970
> change-id: 20231214-options-386e48b6fa4c
>
> Best regards,
next prev parent reply other threads:[~2023-12-18 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 6:31 [PATCH 0/2] qemu-options: Improve -display cocoa documentation Akihiko Odaki
2023-12-14 6:31 ` [PATCH 1/2] qemu-options: Unify the help entries for cocoa Akihiko Odaki
2023-12-14 9:46 ` Philippe Mathieu-Daudé
2023-12-14 6:31 ` [PATCH 2/2] qemu-options: Tell more for -display cocoa Akihiko Odaki
2023-12-18 6:14 ` Markus Armbruster [this message]
2023-12-23 16:33 ` [PATCH 0/2] qemu-options: Improve -display cocoa documentation Michael Tokarev
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=877clcujeu.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=balaton@eik.bme.hu \
--cc=carwynellis@gmail.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.