qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 00/10] Docker patches
Date: Wed, 20 Jul 2016 18:55:09 +0800	[thread overview]
Message-ID: <20160720105509.GA15998@ad.usersys.redhat.com> (raw)
In-Reply-To: <CAFEAcA9TWwrTNfgRCqQCz4HK3oJQF7uB6Lgw5Dm5_D4aBoXVfA@mail.gmail.com>

On Wed, 07/20 11:31, Peter Maydell wrote:
> On 19 July 2016 at 15:31, Fam Zheng <famz@redhat.com> wrote:
> > Hi Peter,
> >
> > The following changes since commit d25321f210f745e428bc5c82f3dfad7a4a95a6ae:
> >
> >   Merge remote-tracking branch 'remotes/jasowang/tags/net-pull-request' into staging (2016-07-19 13:00:35 +0100)
> >
> > are available in the git repository at:
> >
> >   git@github.com:famz/qemu tags/docker-pull-request
> >
> > for you to fetch changes up to 1b596a4f6b5f28533dca315bf3ba178207bb7f23:
> >
> >   docker: pass EXECUTABLE to build script (2016-07-19 22:10:09 +0800)
> >
> > ----------------------------------------------------------------
> >
> > - Alex's qemu-user based debootstrap testing.
> > - Some small improvements.
> >
> > ----------------------------------------------------------------
> 
> Hi; I'm afraid you've forgotten to add your signed-off-by line
> as submaintainer to the patches which were written by Alex.
> Could you fix this and resend, please? (You can just resend the
> cover letter email.)

Amusing. I explicitly checked they are in the emails, which I think are added
by "git format-patch -s". But that is apparently not enough because the tag
doesn't get it.

Resending in a while.

Fam

      reply	other threads:[~2016-07-20 10:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 14:31 [Qemu-devel] [PULL 00/10] Docker patches Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 01/10] tests/docker/docker.py: docker_dir outside build Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 02/10] tests/docker/docker.py: support --include-executable Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 03/10] tests/docker/docker.py: check and run .pre script Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 04/10] tests/docker/dockerfiles: new debian-bootstrap.docker Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 05/10] tests/docker/docker.py: add update operation Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 06/10] docker: More sensible run script Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 07/10] docker: Fix exit code if $CMD failed Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 08/10] docker: Add "images" subcommand to docker.py Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 09/10] docker: Don't start a container that doesn't exist Fam Zheng
2016-08-02 18:59   ` Paolo Bonzini
2016-08-03  2:50     ` Fam Zheng
2016-07-19 14:31 ` [Qemu-devel] [PULL 10/10] docker: pass EXECUTABLE to build script Fam Zheng
2016-07-20 10:31 ` [Qemu-devel] [PULL 00/10] Docker patches Peter Maydell
2016-07-20 10:55   ` Fam Zheng [this message]

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=20160720105509.GA15998@ad.usersys.redhat.com \
    --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).