From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL 0/1] virtio update
Date: Thu, 15 May 2014 19:33:45 +0300 [thread overview]
Message-ID: <20140515163345.GA1242@redhat.com> (raw)
In-Reply-To: <CAFEAcA-XZ-P4mughDDRmmh-gMBsDLY=fKeLVaoUcRuYs8Yjd1g@mail.gmail.com>
On Thu, May 15, 2014 at 05:32:05PM +0100, Peter Maydell wrote:
> On 14 May 2014 04:53, Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > Resending: same as previous pull request but with numbers in the subject.
> > Sorry about the noise.
> >
> >
> > The following changes since commit 06b4f00d53637f2c16a62c2cbaa30bffb045cf88:
> >
> > Merge remote-tracking branch 'remotes/qmp-unstable/queue/qmp' into staging (2014-05-09 15:46:34 +0100)
> >
> > are available in the git repository at:
> >
> >
> > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git for_upstream
> >
> > for you to fetch changes up to 937251408051e0489f78e4db3c92e045b147b38b:
> >
> > virtio: allow mapping up to max queue size (2014-05-12 12:07:21 +0300)
>
> My apply-pullreq script complains:
> merge: remotes/mst/for_upstream - not something we can merge
>
> did you mean "tags/for_upstream" ?
>
> thanks
> -- PMM
Yes: git used to get this right but it looks like it's broken in git
master.
hashes match and it's signed properly ...
want me to resend?
--
MST
next prev parent reply other threads:[~2014-05-15 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 3:53 [Qemu-devel] [PULL 0/1] virtio update Michael S. Tsirkin
2014-05-14 3:53 ` [Qemu-devel] [PULL 1/1] virtio: allow mapping up to max queue size Michael S. Tsirkin
2014-05-15 16:32 ` [Qemu-devel] [PULL 0/1] virtio update Peter Maydell
2014-05-15 16:33 ` Michael S. Tsirkin [this message]
2014-05-15 17:35 ` Peter Maydell
2014-05-17 18:20 ` Michael S. Tsirkin
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=20140515163345.GA1242@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.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 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.