qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/10] Ui 20171011 patches
Date: Thu, 12 Oct 2017 11:14:54 +0100	[thread overview]
Message-ID: <20171012101454.GI16125@redhat.com> (raw)
In-Reply-To: <1507803203.26812.20.camel@redhat.com>

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:
> > >   Hi,
> > > 
> > > > Not AFAICT - if i try it just never completes connect()
> > > 
> > > 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

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-10-12 10:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  8:35 [Qemu-devel] [PULL 00/10] Ui 20171011 patches Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 01/10] build: automatically handle GIT submodule checkout for dtc Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 02/10] docker: don't rely on submodules existing in the main checkout Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 03/10] ui: add keycodemapdb repository as a GIT submodule Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 04/10] ui: convert common input code to keycodemapdb Gerd Hoffmann
2017-10-11  8:35 ` [Qemu-devel] [PULL 05/10] ui: convert key events to QKeyCodes immediately Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 06/10] ui: don't export qemu_input_event_new_key Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 07/10] tools: add qemu-keymap Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 08/10] Add pc-bios/keymaps/Makefile Gerd Hoffmann
2017-10-11  8:36 ` [Qemu-devel] [PULL 10/10] ui/gtk: Fix deprecation of vte_terminal_copy_clipboard Gerd Hoffmann
2017-10-11 14:37 ` [Qemu-devel] [PULL 00/10] Ui 20171011 patches Peter Maydell
2017-10-11 14:49   ` Kamil Rytarowski
2017-10-11 15:49   ` Daniel P. Berrange
2017-10-11 16:45     ` Peter Maydell
2017-10-12  8:24       ` Daniel P. Berrange
2017-10-12  9:00         ` Peter Maydell
2017-10-12  9:30         ` Gerd Hoffmann
2017-10-12  9:33           ` Daniel P. Berrange
2017-10-12 10:04             ` Gerd Hoffmann
2017-10-12 10:07               ` Daniel P. Berrange
2017-10-12 10:11                 ` Peter Maydell
2017-10-12 10:13                 ` Gerd Hoffmann
2017-10-12 10:14                   ` Daniel P. Berrange [this message]
2017-10-12  9:51           ` Peter Maydell
2017-10-12 10:01   ` Gerd Hoffmann
2017-10-13  8:15   ` Gerd Hoffmann

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=20171012101454.GI16125@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@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).