Am 24.05.2014 um 23:24 hat Max Reitz geschrieben:
> This series enables qemu-iotests to be run in a build tree outside of
> the source tree. It also makes the tests use the command for invoking
> the Python interpreter specified through configure instead of always
> using "/usr/bin/env python".
Th
Max Reitz writes:
> On 07.06.2014 23:21, Max Reitz wrote:
>> On 24.05.2014 23:24, Max Reitz wrote:
>>> This series enables qemu-iotests to be run in a build tree outside of
>>> the source tree. It also makes the tests use the command for invoking
>>> the Python interpreter specified through confi
On 07.06.2014 23:21, Max Reitz wrote:
On 24.05.2014 23:24, Max Reitz wrote:
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr
On 24.05.2014 23:24, Max Reitz wrote:
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr/bin/env python".
Ping; I do understa
On 24.05.2014 23:24, Max Reitz wrote:
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr/bin/env python".
v4:
- Patch 1:
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr/bin/env python".
v4:
- Patch 1:
- fixed a comment ("assume that it truly
