From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: el13635@mail.ntua.gr, kwolf@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: fix bs->file leak in bdrv_new_open_driver()
Date: Fri, 7 Jul 2017 08:05:23 +0800 [thread overview]
Message-ID: <20170707000523.GK5149@lemon.lan> (raw)
In-Reply-To: <149938496797.27.11708429179775046632@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/20170629060300.29869-1-el13635@mail.ntua.gr' 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/20170629060300.29869-1-el13635@mail.ntua.gr', '-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:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 6:03 [Qemu-devel] [PATCH] block: fix bs->file leak in bdrv_new_open_driver() Manos Pitsidianakis
2017-06-29 11:18 ` Kevin Wolf
2017-06-29 12:07 ` Manos Pitsidianakis
2017-06-29 13:57 ` Kevin Wolf
2017-06-29 20:06 ` Manos Pitsidianakis
2017-07-07 9:28 ` Kevin Wolf
2017-07-07 9:53 ` Manos Pitsidianakis
2017-07-06 23:49 ` no-reply
2017-07-07 0:05 ` 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=20170707000523.GK5149@lemon.lan \
--to=famz@redhat.com \
--cc=el13635@mail.ntua.gr \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).