From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Glauber Costa <glommer@gmail.com>, Alex Graf <alex@csgraf.de>,
qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>
Subject: [Qemu-devel] Re: [PATCH 1/4] Add GPL bios as a submodule
Date: Sun, 17 May 2009 18:43:00 +0300 [thread overview]
Message-ID: <4A103084.2000508@redhat.com> (raw)
In-Reply-To: <1242574141-18488-2-git-send-email-aliguori@us.ibm.com>
Anthony Liguori wrote:
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> ---
> .gitmodules | 3 +++
> roms/gplbios | 1 +
> 2 files changed, 4 insertions(+), 0 deletions(-)
> create mode 100644 .gitmodules
> create mode 160000 roms/gplbios
>
> diff --git a/.gitmodules b/.gitmodules
> new file mode 100644
> index 0000000..9bdf196
> --- /dev/null
> +++ b/.gitmodules
> @@ -0,0 +1,3 @@
> +[submodule "roms/gplbios"]
> + path = roms/gplbios
> + url = git://repo.or.cz/gplbios/qemu.git
>
I really prefer a relative path here, so that people can set up mirrors
on an internal server. Also, not everyone can access the git port. It
can be worked around, but it's much better to have things working out of
the proverbial box.
Also, s/roms/firmware/ to be modern.
Having said all that, I'd rather see seabios here. Sure, it will take
us time to add missing features, if any, but life will be much more
pleasant afterwards. We should reduce our ties to the bochs bios, not
tighten them.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-17 15:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 15:28 [Qemu-devel] [PATCH 0/4][RFC] Bring ROM source into tree via git submodules Anthony Liguori
2009-05-17 15:28 ` [Qemu-devel] [PATCH 1/4] Add GPL bios as a submodule Anthony Liguori
2009-05-17 15:43 ` Avi Kivity [this message]
2009-05-17 15:49 ` [Qemu-devel] " Anthony Liguori
2009-05-17 16:23 ` Avi Kivity
2009-05-17 17:51 ` Jamie Lokier
2009-05-17 18:03 ` Avi Kivity
2009-05-17 18:05 ` Stanislav
2009-05-17 18:11 ` Avi Kivity
2009-05-17 18:37 ` Stanislav
2009-05-17 19:07 ` Avi Kivity
2009-05-17 22:12 ` Carl-Daniel Hailfinger
2009-05-17 22:40 ` Avi Kivity
2009-05-17 23:22 ` Anthony Liguori
2009-05-18 15:20 ` ron minnich
2009-05-18 2:40 ` Kevin O'Connor
2009-05-17 23:13 ` Anthony Liguori
2009-05-18 4:22 ` Jamie Lokier
2009-05-25 13:04 ` Carl-Daniel Hailfinger
2009-05-17 23:09 ` Anthony Liguori
2009-05-17 23:23 ` Avi Kivity
2009-05-17 23:31 ` Anthony Liguori
2009-05-17 23:40 ` Avi Kivity
2009-05-18 1:17 ` Anthony Liguori
2009-05-18 5:48 ` Avi Kivity
2009-05-17 17:10 ` Sebastian Herbszt
2009-05-17 15:28 ` [Qemu-devel] [PATCH 2/4] Add submodule for VGABios Anthony Liguori
2009-05-17 15:29 ` [Qemu-devel] [PATCH 3/4] Update makefile to build roms Anthony Liguori
2009-05-17 15:46 ` [Qemu-devel] " Avi Kivity
2009-05-17 15:47 ` Avi Kivity
2009-05-17 15:53 ` Anthony Liguori
2009-05-17 17:16 ` Avi Kivity
2009-05-17 23:10 ` Anthony Liguori
2009-05-17 22:04 ` Paul Brook
2009-05-17 23:28 ` Anthony Liguori
2009-05-17 23:43 ` Paul Brook
2009-05-18 1:18 ` Anthony Liguori
2009-05-18 4:24 ` Jamie Lokier
2009-05-18 8:25 ` Riku Voipio
2009-05-18 8:35 ` Avi Kivity
2009-05-17 15:29 ` [Qemu-devel] [PATCH 4/4] Allow tool chain to be specified for bios build Anthony Liguori
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=4A103084.2000508@redhat.com \
--to=avi@redhat.com \
--cc=alex@csgraf.de \
--cc=aliguori@us.ibm.com \
--cc=glommer@gmail.com \
--cc=kirkland@canonical.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).