From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Jeff Cody <jcody@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror
Date: Tue, 20 Feb 2018 23:01:10 +0100 [thread overview]
Message-ID: <5059119b-6ec4-88e9-6d92-5edb7c22fbb8@redhat.com> (raw)
In-Reply-To: <CAFEAcA887ukS-r6ECRG7rrCMzXO8PpJqjevR=sELc_LNfRazLA@mail.gmail.com>
On 20/02/2018 19:43, Peter Maydell wrote:
> I just noticed that we seem to have acquired another git
> submodule that isn't pointing to a qemu.org git url:
>
> [submodule "roms/seabios-hppa"]
> path = roms/seabios-hppa
> url = git://github.com/hdeller/seabios-hppa.git
>
> Jeff, could we set up so we can mirror this repo on qemu.org?
> Then we can send a patch to update the .gitmodules to point to it.
This is a fork of SeaBIOS, perhaps we should add "branch = hppa" and
pull it into the existing SeaBIOS repo of qemu.git.
However, I am worried that any bugfixes are never going to be applied to
the HPPA version. How much forked is the fork?
Paolo
next prev parent reply other threads:[~2018-02-20 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:43 [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror Peter Maydell
2018-02-20 21:41 ` BALATON Zoltan
2018-02-20 21:55 ` Paolo Bonzini
2018-02-20 22:12 ` BALATON Zoltan
2018-02-20 22:01 ` Paolo Bonzini [this message]
2018-02-21 5:27 ` Jeff Cody
2018-03-19 13:19 ` Peter Maydell
2018-03-19 13:32 ` BALATON Zoltan
2018-03-19 19:15 ` Jeff Cody
2018-03-19 21:36 ` BALATON Zoltan
2018-03-19 19:06 ` Jeff Cody
2018-03-20 17:54 ` Paolo Bonzini
2018-03-21 15:09 ` Jeff Cody
2018-03-21 15:21 ` Paolo Bonzini
2018-03-21 15:34 ` Jeff Cody
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=5059119b-6ec4-88e9-6d92-5edb7c22fbb8@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcody@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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).