From: Peter Maydell <peter.maydell@linaro.org>
To: Jeff Cody <jcody@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] qemu.org: new git repos to be mirrored (qemu-palcode, capstone, keycodemapdb)
Date: Thu, 12 Oct 2017 13:42:54 +0100 [thread overview]
Message-ID: <CAFEAcA81AZBaGu6nrLK51_6vWApMSpMDhb9OsnkdApMGebYK8w@mail.gmail.com> (raw)
On 12 October 2017 at 11:14, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Thu, Oct 12, 2017 at 12:13:23PM +0200, Gerd Hoffmann wrote:
>> On Thu, 2017-10-12 at 11:07 +0100, Daniel P. Berrange wrote:
>> > On Thu, Oct 12, 2017 at 12:04:47PM +0200, Gerd Hoffmann wrote:
>> > > Hmm, so maybe we should mirror the thing on git.qemu.org and use
>> > > that?
>> >
>> > Can that be made 100% automated - I don't want to have to push
>> > changes to
>> > two different git repos.
>>
>> Yes, seabios works that way for example.
>
> Ok, lets do that mirror then we can use git:// and we're consistent with
> other submodules we use
We also have RTH's capstone disassembler patchset which wants to
use capstone as a more-or-less-required dependency, and we have
the one loose end in our current submodules that the qemu-palcode
rom is using a non-qemu.org URL.
So can we set up these repos to be mirrored on qemu.org:
* git://github.com/rth7680/qemu-palcode.git
* https://github.com/aquynh/capstone.git
* https://gitlab.com/keycodemap/keycodemapdb.git
please?
thanks
-- PMM
next reply other threads:[~2017-10-12 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 12:42 Peter Maydell [this message]
2017-10-12 14:01 ` [Qemu-devel] qemu.org: new git repos to be mirrored (qemu-palcode, capstone, keycodemapdb) Jeff Cody
2017-10-12 14:16 ` Peter Maydell
2017-10-12 14:42 ` Paolo Bonzini
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=CAFEAcA81AZBaGu6nrLK51_6vWApMSpMDhb9OsnkdApMGebYK8w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=jcody@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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.