From: Fam Zheng <famz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v4 00/38] Test and build patches
Date: Fri, 15 Sep 2017 19:36:11 +0800 [thread overview]
Message-ID: <20170915113611.GI17199@lemon> (raw)
In-Reply-To: <CAFEAcA_b71j3v5Ag7uSTPBgUT2_Qej+KJxH57cKV+6QdRgCw9A@mail.gmail.com>
On Fri, 09/15 11:55, Peter Maydell wrote:
> On 15 September 2017 at 10:02, Fam Zheng <famz@redhat.com> wrote:
> > The following changes since commit 04ef33052c205170c92df21ca0b4be4f3b102188:
> >
> > tcg/tci: do not use ldst label (never implemented) (2017-09-11 19:24:05 +0100)
> >
> > are available in the git repository at:
> >
> > git://github.com/famz/qemu.git tags/test-and-build-pull-request
> >
> > for you to fetch changes up to be78fe670401af14e6d63fce5c5467f751207871:
> >
> > buildsys: Move rdma libs to per object (2017-09-15 15:05:24 +0800)
> >
> > ----------------------------------------------------------------
> >
> > ----------------------------------------------------------------
> >
> > Alex Bennée (4):
> > docker: ensure NOUSER for travis images
> > docker: docker.py make --no-cache skip checksum test
> > docker: don't install device-tree-compiler build-deps in travis.docker
> > docker: reduce noise when building travis.docker
> >
> > Fam Zheng (34):
> > docker: Update ubuntu image
> > docker: Enable features explicitly in test-full
> > tests/docker: Clean up paths
> > gitignore: Ignore vm test images
> > qemu.py: Add "wait()" method
> > scripts: Add archive-source.sh
> > tests: Add a test key pair
>
> So, before I commit an ssh private key to our git repo,
> can you explain why it's ok that this is public? The
> commit message for the relevant patch doesn't really say.
It's under tests/, and the key is only used to access a temporarily spawned test
VM.
Fam
next prev parent reply other threads:[~2017-09-15 11:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 9:02 [Qemu-devel] [PULL v4 00/38] Test and build patches Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 10/38] scripts: Add archive-source.sh Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 11/38] tests: Add a test key pair Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 12/38] tests: Add vm test lib Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 13/38] tests: Add ubuntu.i386 image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 14/38] tests: Add FreeBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 15/38] tests: Add NetBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 16/38] tests: Add OpenBSD image Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 17/38] Makefile: Add rules to run vm tests Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 18/38] MAINTAINERS: Add tests/vm entry Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 19/38] tests: Add README for vm tests Fam Zheng
2017-09-15 9:02 ` [Qemu-devel] [PULL v4 20/38] docker: Use archive-source.py Fam Zheng
2017-09-15 10:55 ` [Qemu-devel] [PULL v4 00/38] Test and build patches Peter Maydell
2017-09-15 11:36 ` Fam Zheng [this message]
2017-09-15 11:40 ` Daniel P. Berrange
2017-09-15 12:03 ` Peter Maydell
2017-09-15 12:09 ` Daniel P. Berrange
2017-09-15 12:21 ` Fam Zheng
2017-09-15 12:31 ` Daniel P. Berrange
2017-09-15 12:51 ` Fam Zheng
2017-09-15 14:47 ` Philippe Mathieu-Daudé
2017-09-15 20:52 ` Fam Zheng
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=20170915113611.GI17199@lemon \
--to=famz@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).