, git diff vs a format-patch.
Subject: [PATCH] tests/vm: update openbsd to release 6.8
A double dash at the end of a package name removes ambiguity
when the intent is to install a non-FLAVORed package.
Signed-off-by: Brad Smith
Reviewed-by: Gerd Hoffmann
Tested-by: Gerd Hoffmann
Reviewed-by: Phi
e addressed,
>>> - the tags are correct.
>>>
>>> The patch format itself seems broken... Like a copy/paste
>>> into an email client...
>> Well, git diff vs a format-patch.
>>
>>
>> Subject: [PATCH] tests/vm: update openbsd to releas
copy/paste
into an email client...
Well, git diff vs a format-patch.
Subject: [PATCH] tests/vm: update openbsd to release 6.8
A double dash at the end of a package name removes ambiguity
when the intent is to install a non-FLAVORed package.
Signed-off-by: Brad Smith
Reviewed-by: Gerd Hoffmann
tags are correct.
>
> The patch format itself seems broken... Like a copy/paste
> into an email client...
Well, git diff vs a format-patch.
Subject: [PATCH] tests/vm: update openbsd to release 6.8
A double dash at the end of a package name removes ambiguity
when the intent is to install
On 10/27/20 6:30 AM, Brad Smith wrote:
> tests/vm: update openbsd to release 6.8
>
> A double dash at the end of a package name removes ambiguity
> when the intent is to install a non-FLAVORed package.
>
> Signed-off-by: Brad Smith
> Reviewed-by: Gerd Hoffmann
> Tested-by: Gerd Hoffmann
> Revi
tests/vm: update openbsd to release 6.8
A double dash at the end of a package name removes ambiguity
when the intent is to install a non-FLAVORed package.
Signed-off-by: Brad Smith
Reviewed-by: Gerd Hoffmann
Tested-by: Gerd Hoffmann
Reviewed-by: Philippe Mathieu-Daud??
diff --git a/tests/vm
