From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] RFC: changing ROM bundling in tar dists for releases
Date: Fri, 01 Sep 2017 16:11:44 +0200 [thread overview]
Message-ID: <1504275104.10150.19.camel@redhat.com> (raw)
In-Reply-To: <1504254677.10150.3.camel@redhat.com>
Hi,
> I think it makes sense to create a separate project for the firmware
> blobs. Move over the firmware binaries and source submodules to the
> new project. This way updating both firmware sources and binaries
> can
> be done with a single commit, like we handle this today, just in the
> new firmware repo instead of the main qemu repo.
i.e. something like this:
https://www.kraxel.org/cgit/qemu-firmware/
(only seabios is there for now)
cheers,
Gerd
next prev parent reply other threads:[~2017-09-01 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 12:29 [Qemu-devel] RFC: changing ROM bundling in tar dists for releases Daniel P. Berrange
2017-08-31 12:49 ` Peter Maydell
2017-09-01 8:31 ` Gerd Hoffmann
2017-09-01 9:24 ` Daniel P. Berrange
2017-09-01 9:49 ` Gerd Hoffmann
2017-09-01 11:00 ` Peter Maydell
2017-09-01 14:11 ` Gerd Hoffmann [this message]
2017-09-01 15:13 ` Daniel P. Berrange
2017-09-01 17:45 ` Gerd Hoffmann
2017-08-31 15:47 ` Philippe Mathieu-Daudé
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=1504275104.10150.19.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.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).