On 11/13/2015 03:26 AM, Stefan Hajnoczi wrote:
> On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
>> Commit 6c6f312d added a new test, but did not mark it for
>> exclusion in .gitignore.
>>
>> Signed-off-by: Eric Blake
>> ---
>>
>> Yeah, I know this affects only non-VPATH builds, which
On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
> Commit 6c6f312d added a new test, but did not mark it for
> exclusion in .gitignore.
>
> Signed-off-by: Eric Blake
> ---
>
> Yeah, I know this affects only non-VPATH builds, which we don't
> recommend, but we might as well be consiste
On 11/12/2015 07:27 PM, Stefan Hajnoczi wrote:
> On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
>> Commit 6c6f312d added a new test, but did not mark it for
>> exclusion in .gitignore.
>>
>> Signed-off-by: Eric Blake
>> ---
>>
>> Yeah, I know this affects only non-VPATH builds, which
On Thu, Nov 12, 2015 at 11:33:48AM -0700, Eric Blake wrote:
> Commit 6c6f312d added a new test, but did not mark it for
> exclusion in .gitignore.
>
> Signed-off-by: Eric Blake
> ---
>
> Yeah, I know this affects only non-VPATH builds, which we don't
> recommend, but we might as well be consiste
Commit 6c6f312d added a new test, but did not mark it for
exclusion in .gitignore.
Signed-off-by: Eric Blake
---
Yeah, I know this affects only non-VPATH builds, which we don't
recommend, but we might as well be consistent.
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/t