From: Peter Maydell <peter.maydell@linaro.org>
To: Jeff Cody <jcody@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Richard Henderson <rth@twiddle.net>, BALATON Zoltan <balaton@eik.bme.hu>
Subject: [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror
Date: Tue, 20 Feb 2018 18:43:22 +0000 [thread overview]
Message-ID: <CAFEAcA887ukS-r6ECRG7rrCMzXO8PpJqjevR=sELc_LNfRazLA@mail.gmail.com> (raw)
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.
(There's also a patchset on list that wants to add a
submodule for git://github.com/zbalaton/u-boot-sam460ex
but I don't know if that will go in or not yet. Should
we insist that we set up the mirror first for new
submodules, or allow them in and fix things up after?
By default we're doing the latter at the moment; the
former seems cleaner but makes it more painful for
contributors to get things added which need new
submodules.)
thanks
-- PMM
next reply other threads:[~2018-02-20 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:43 Peter Maydell [this message]
2018-02-20 21:41 ` [Qemu-devel] Moving seabios-hppa git submodule to use a qemu.org mirror BALATON Zoltan
2018-02-20 21:55 ` Paolo Bonzini
2018-02-20 22:12 ` BALATON Zoltan
2018-02-20 22:01 ` Paolo Bonzini
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='CAFEAcA887ukS-r6ECRG7rrCMzXO8PpJqjevR=sELc_LNfRazLA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=jcody@redhat.com \
--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 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.