On 02/24/2018 10:26 AM, MacDonald, Joe wrote:
> Hey Armin,
>
> Your branch includes at least some (I haven't looked to see if it's
> all, seems likely) of the changes I have merged and ready to include
> for meta-networking. Since I haven't pushed them yet and wouldn't be
> before tonight at the
On Sat, Feb 24, 2018 at 09:56:42AM -0800, akuster808 wrote:
> Hello,
>
> I am planning on moving some recipes to new locations that are more
> in-line with their function.
>
> Also, I plan on adding *-shells, *-dbs, *-security and *.crypto and
> moving the appropriate recipes there.
>
> This
Hey Armin,
Your branch includes at least some (I haven't looked to see if it's all, seems
likely) of the changes I have merged and ready to include for meta-networking.
Since I haven't pushed them yet and wouldn't be before tonight at the earliest,
do you want me to wait? Or were they just
Hello,
I am planning on moving some recipes to new locations that are more
in-line with their function.
Also, I plan on adding *-shells, *-dbs, *-security and *.crypto and
moving the appropriate recipes there.
This might help facilitate folks signing up to maintain a grouping like
Yes we can or we can wait for next vbox release which will hopefully
include support for 4.15 as suggested in Upstream-Status.
On Sat, Feb 24, 2018 at 4:57 PM, Khem Raj wrote:
> On Sat, Feb 24, 2018 at 2:51 AM, Martin Jansa
> wrote:
> > * 5.1.26
On Sat, Feb 24, 2018 at 2:51 AM, Martin Jansa wrote:
> * 5.1.26 doesn't build with 4.15 kernel
>
> Signed-off-by: Martin Jansa
> ---
> .../linux-4.15.0-rc8-VBoxGuestAdditions-amd64.diff | 90
> ++
> ...drivers_5.1.26.bb =>
* 5.1.26 doesn't build with 4.15 kernel
Signed-off-by: Martin Jansa
---
.../linux-4.15.0-rc8-VBoxGuestAdditions-amd64.diff | 90 ++
...drivers_5.1.26.bb => vboxguestdrivers_5.2.6.bb} | 22 --
2 files changed, 107 insertions(+), 5 deletions(-)