[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part
From: |
Fam Zheng |
Subject: |
Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part |
Date: |
Fri, 7 Jul 2017 08:06:05 +0800 |
User-agent: |
Mutt/1.8.0 (2017-02-23) |
On Thu, 07/06 16:48, address@hidden wrote:
> fatal: Cannot update paths and switch to branch 'test' at the same time.
> Did you intend to checkout 'origin/patchew/address@hidden' 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/address@hidden', '-b', 'test']' returned non-zero exit status
> 128
Ignore this please, patchew is recovering from a bad state.
- [Qemu-devel] [PATCH 06/11] block: add a few more notes on locking, (continued)
- [Qemu-devel] [PATCH 06/11] block: add a few more notes on locking, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 09/11] block/replication: do not acquire AioContext, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 07/11] block: do not acquire AioContext in check_to_replace_node, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 10/11] block: do not take AioContext around reopen, Paolo Bonzini, 2017/07/06
- [Qemu-devel] [PATCH 11/11] block/snapshot: do not take AioContext lock, Paolo Bonzini, 2017/07/06
- Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part, no-reply, 2017/07/06
- Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part,
Fam Zheng <=
- Re: [Qemu-devel] [RFC PATCH 00/11] Block layer thread-safety, next part, Stefan Hajnoczi, 2017/07/10