On Fri, Oct 27, 2017 at 03:10:17PM +1100, Alexey Kardashevskiy wrote:
> On 27/10/17 00:33, Philippe Mathieu-Daudé wrote:
> > On 10/26/2017 10:04 AM, Daniel P. Berrange wrote:
> >> Some people building QEMU use VPATH builds where the source directory is
> >> on a
> >> read-only volume. In such a ca
On 27/10/17 00:04, Daniel P. Berrange wrote:
> Some people building QEMU use VPATH builds where the source directory is on a
> read-only volume. In such a case 'scripts/git-submodules.sh update' will
> always
> fail and users are required to run it manually themselves on their original
> writable
On 27/10/17 00:33, Philippe Mathieu-Daudé wrote:
> On 10/26/2017 10:04 AM, Daniel P. Berrange wrote:
>> Some people building QEMU use VPATH builds where the source directory is on a
>> read-only volume. In such a case 'scripts/git-submodules.sh update' will
>> always
>> fail and users are required
On 10/26/2017 10:04 AM, Daniel P. Berrange wrote:
> Some people building QEMU use VPATH builds where the source directory is on a
> read-only volume. In such a case 'scripts/git-submodules.sh update' will
> always
> fail and users are required to run it manually themselves on their original
> writ
Some people building QEMU use VPATH builds where the source directory is on a
read-only volume. In such a case 'scripts/git-submodules.sh update' will always
fail and users are required to run it manually themselves on their original
writable source directory.
While this is already supported, it i
