From: Alyssa Ross <hi@alyssa.is>
To: Gurchetan Singh <gurchetansingh@chromium.org>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, akihiko.odaki@gmail.com,
ray.huang@amd.com, alex.bennee@linaro.org, shentey@gmail.com,
ernunes@redhat.com, manos.pitsidianakis@linaro.org,
philmd@linaro.org
Subject: Re: [PATCH v11 0/9] rutabaga_gfx + gfxstream
Date: Wed, 23 Aug 2023 11:07:26 +0000 [thread overview]
Message-ID: <87a5uiyq35.fsf@alyssa.is> (raw)
In-Reply-To: <20230823012541.485-1-gurchetansingh@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Gurchetan Singh <gurchetansingh@chromium.org> writes:
> - Official "release commits" issued for rutabaga_gfx_ffi,
> gfxstream, aemu-base. For example, see crrev.com/c/4778941
>
> - The release commits can make packaging easier, though once
> again all known users will likely just build from sources
> anyways
It's a small thing, but could there be actual tags, rather than just
blessed commits? It'd just make them easier to find, and save a bit of
time in review for packages.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-08-23 11:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 1:25 [PATCH v11 0/9] rutabaga_gfx + gfxstream Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 1/9] virtio: Add shared memory capability Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 2/9] virtio-gpu: CONTEXT_INIT feature Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 3/9] virtio-gpu: hostmem Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 4/9] virtio-gpu: blob prep Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 5/9] gfxstream + rutabaga prep: added need defintions, fields, and options Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 6/9] gfxstream + rutabaga: add initial support for gfxstream Gurchetan Singh
2023-08-23 9:59 ` Akihiko Odaki
2023-09-13 11:57 ` Bernhard Beschow
2023-09-14 4:38 ` Gurchetan Singh
2023-09-14 7:23 ` Bernhard Beschow
2023-09-15 2:38 ` Gurchetan Singh
2023-09-19 18:36 ` Bernhard Beschow
2023-09-19 22:07 ` Akihiko Odaki
2023-09-21 23:44 ` Gurchetan Singh
2023-09-22 2:41 ` Akihiko Odaki
2023-09-29 15:06 ` Bernhard Beschow
2023-09-30 10:28 ` Thomas Huth
2023-10-09 11:18 ` Markus Armbruster
2023-09-27 11:34 ` Thomas Huth
2023-09-27 12:33 ` Markus Armbruster
2023-08-23 1:25 ` [PATCH v11 7/9] gfxstream + rutabaga: meson support Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 8/9] gfxstream + rutabaga: enable rutabaga Gurchetan Singh
2023-08-23 1:25 ` [PATCH v11 9/9] docs/system: add basic virtio-gpu documentation Gurchetan Singh
2023-08-23 11:07 ` Alyssa Ross [this message]
2023-08-24 23:56 ` [PATCH v11 0/9] rutabaga_gfx + gfxstream Gurchetan Singh
2023-08-25 7:11 ` Alyssa Ross
2023-08-25 19:05 ` Gurchetan Singh
2023-08-25 19:29 ` Alyssa Ross
2023-08-25 19:37 ` Alyssa Ross
2023-08-29 0:43 ` Gurchetan Singh
2023-09-12 8:53 ` Alyssa Ross
2023-09-13 1:14 ` Gurchetan Singh
2023-09-13 10:10 ` Alyssa Ross
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=87a5uiyq35.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=akihiko.odaki@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=ernunes@redhat.com \
--cc=gurchetansingh@chromium.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ray.huang@amd.com \
--cc=shentey@gmail.com \
/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).