From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: bobby.prani@gmail.com, ehabkost@redhat.com, pbonzini@redhat.com,
alex.bennee@linaro.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/2] Pending MTTCG patches
Date: Fri, 7 Jul 2017 08:03:37 +0800 [thread overview]
Message-ID: <20170707000337.GF5149@lemon.lan> (raw)
In-Reply-To: <149938497583.27.16642480181912501797@7a482c8a7db2>
On Thu, 07/06 16:49, no-reply@patchew.org wrote:
> Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
> fatal: Cannot update paths and switch to branch 'test' at the same time.
> Did you intend to checkout 'origin/patchew/20170629071129.29362-1-bobby.prani@gmail.com' which can not be resolved as commit?
> Traceback (most recent call last):
> File "/home/fam/bin/patchew", line 440, in test_one
> git_clone_repo(clone, r["repo"], r["head"], logf)
> File "/home/fam/bin/patchew", line 53, in git_clone_repo
> cwd=clone)
> File "/usr/lib64/python3.5/subprocess.py", line 271, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['git', 'checkout', 'origin/patchew/20170629071129.29362-1-bobby.prani@gmail.com', '-b', 'test']' returned non-zero exit status 128
Ignore this please, patchew is recovering from a bad state.
prev parent reply other threads:[~2017-07-07 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:11 [Qemu-devel] [PATCH 0/2] Pending MTTCG patches Pranith Kumar
2017-06-29 7:11 ` [Qemu-devel] [PATCH v3 1/2] Revert "exec.c: Fix breakpoint invalidation race" Pranith Kumar
2017-06-29 7:11 ` [Qemu-devel] [PATCH v3 2/2] mttcg/i386: Patch instruction using async_safe_* framework Pranith Kumar
2017-07-07 10:02 ` Alex Bennée
2017-07-07 10:26 ` Paolo Bonzini
2017-07-06 23:49 ` [Qemu-devel] [PATCH 0/2] Pending MTTCG patches no-reply
2017-07-07 0:03 ` 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=20170707000337.GF5149@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.