Riku Voipio writes:
> On 13 June 2016 at 15:30, Alex Bennée wrote:
>>
>> Riku Voipio writes:
>>
>>> On 13 June 2016 at 12:22, Alex Bennée wrote:
Fam Zheng writes:
> On Wed, 06/08 17:35, Alex Bennée wrote:
>> Hi,
>>
>> This is a re-spin of the previous series bu
On 13 June 2016 at 15:30, Alex Bennée wrote:
>
> Riku Voipio writes:
>
>> On 13 June 2016 at 12:22, Alex Bennée wrote:
>>>
>>> Fam Zheng writes:
>>>
On Wed, 06/08 17:35, Alex Bennée wrote:
> Hi,
>
> This is a re-spin of the previous series built on top of
> fam/docker.next.
Riku Voipio writes:
> On 13 June 2016 at 12:22, Alex Bennée wrote:
>>
>> Fam Zheng writes:
>>
>>> On Wed, 06/08 17:35, Alex Bennée wrote:
Hi,
This is a re-spin of the previous series built on top of
fam/docker.next. I've made the changes suggested in the last review
an
On 13 June 2016 at 12:22, Alex Bennée wrote:
>
> Fam Zheng writes:
>
>> On Wed, 06/08 17:35, Alex Bennée wrote:
>>> Hi,
>>>
>>> This is a re-spin of the previous series built on top of
>>> fam/docker.next. I've made the changes suggested in the last review
>>> and split the first patch apart to s
On Mon, 06/13 10:22, Alex Bennée wrote:
>
> Fam Zheng writes:
>
> > On Wed, 06/08 17:35, Alex Bennée wrote:
> >> Hi,
> >>
> >> This is a re-spin of the previous series built on top of
> >> fam/docker.next. I've made the changes suggested in the last review
> >> and split the first patch apart to
Fam Zheng writes:
> On Wed, 06/08 17:35, Alex Bennée wrote:
>> Hi,
>>
>> This is a re-spin of the previous series built on top of
>> fam/docker.next. I've made the changes suggested in the last review
>> and split the first patch apart to separate (and fix) the build
>> directory changes first.
On Wed, 06/08 17:35, Alex Bennée wrote:
> Hi,
>
> This is a re-spin of the previous series built on top of
> fam/docker.next. I've made the changes suggested in the last review
> and split the first patch apart to separate (and fix) the build
> directory changes first.
>
> Now it no longer messes
Hi,
This is a re-spin of the previous series built on top of
fam/docker.next. I've made the changes suggested in the last review
and split the first patch apart to separate (and fix) the build
directory changes first.
Now it no longer messes with the docker file you can actually
cross-build tests
