On Wed, Feb 26, 2020 at 08:33:53AM +, Stuart Henderson wrote:
> On 2020/02/26 09:01, Stefan Sperling wrote:
> > On Wed, Feb 26, 2020 at 01:56:15AM +0100, Matthias Kilian wrote:
> > > But i have a (little bit offtopic) question related to what grub
> > > did: my ports build machine still has
On 2020/02/26 09:01, Stefan Sperling wrote:
> On Wed, Feb 26, 2020 at 01:56:15AM +0100, Matthias Kilian wrote:
> > But i have a (little bit offtopic) question related to what grub
> > did: my ports build machine still has that setup with 4 different
> > OpenBSD installations (and64-current,
On Wed, Feb 26, 2020 at 01:56:15AM +0100, Matthias Kilian wrote:
> But i have a (little bit offtopic) question related to what grub
> did: my ports build machine still has that setup with 4 different
> OpenBSD installations (and64-current, i386-current/amd64-stable,
> i386-stable), with some
On Wed, Feb 26, 2020 at 12:31:12AM +0100, Klemens Nanni wrote:
> i386 only, BROKEN since 2017 with clang and ports-gcc, dead upstream
> (GRUB2 is the thing, if at all).
> Any objections? OK?
ok kmos
--Kurt
Hi,
On Wed, Feb 26, 2020 at 12:31:12AM +0100, Klemens Nanni wrote:
> i386 only, BROKEN since 2017 with clang and ports-gcc, dead upstream
> (GRUB2 is the thing, if at all).
>
> Any objections? OK?
Feel free to burn it with fire.
But i have a (little bit offtopic) question related to what grub
i386 only, BROKEN since 2017 with clang and ports-gcc, dead upstream
(GRUB2 is the thing, if at all).
Any objections? OK?
