All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB 2.06 release
Date: Sat, 7 Mar 2020 17:29:20 +0100	[thread overview]
Message-ID: <20200307162920.GA4325@xps> (raw)
In-Reply-To: <20200305135039.pyzcdnpx3psymh7p@tomti.i.net-space.pl>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Thu, Mar 05, 2020 at 02:50:39PM +0100, Daniel Kiper wrote:
> On Wed, Mar 04, 2020 at 05:39:10AM +0100, Patrick Steinhardt wrote:
> > Any chance to get the Arogn2 changes in? As far as I remember we were
> 
> Let's try... We will see how it goes. If you run over the freeze date
> then I can give you an exception. However, not so long...
> 
> > pending some legal issues where you've reached out to GNU, right? Please
> 
> Yeah, I sent your question to FSF folks a few days ago. Sadly, still no reply...
> 
> > correct me if I'm wrong here and you're waiting for me on anything
> > there.
> 
> What about this UEFI allocator thing? Anyway, I would suggest posting
> next version for review now. Then we should have code quite quickly
> hammered out. Legal stuff should not take long if we get a reply which
> we more or less expect what it will be.

I forgot about that, thanks for reminding me. I'll have a look tomorrow
at whether I'm able to get it working as I interpret Leif's vision. By
the way, do you happen to know if other platforms will be impacted by
the increased memory requirement, too?

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-07 16:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 15:01 GRUB 2.06 release Daniel Kiper
2020-02-20  8:46 ` John Paul Adrian Glaubitz
2020-02-25 13:15   ` John Paul Adrian Glaubitz
2020-02-28 12:46     ` Daniel Kiper
2020-02-28 18:26       ` Matt Turner
2020-02-29  1:40       ` Mike Gilbert
2020-03-03 17:26 ` Daniel Kiper
2020-03-03 17:33   ` John Paul Adrian Glaubitz
2020-03-05 13:34     ` Daniel Kiper
2020-03-04  4:39   ` Patrick Steinhardt
2020-03-05 13:50     ` Daniel Kiper
2020-03-07 16:29       ` Patrick Steinhardt [this message]
2020-03-11 10:47   ` Daniel Kiper
2020-03-16 16:41     ` Daniel Kiper
2020-04-22 10:24       ` Daniel Kiper
2020-05-29 12:07         ` Daniel Kiper
2020-07-29 17:46           ` Daniel Kiper
2020-10-19 16:30             ` Pete Batard
2020-10-20 19:00               ` Julian Andres Klode
2020-10-20 19:12                 ` Eli Schwartz
2020-10-20 20:05                   ` Julian Andres Klode
2020-10-20 20:33                     ` Eli Schwartz
2020-10-20 20:06                   ` Pete Batard
2020-10-20 20:03                 ` Pete Batard
2020-12-14 12:39             ` Daniel Kiper
2020-12-14 12:44               ` John Paul Adrian Glaubitz
2020-12-23 23:25               ` Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200307162920.GA4325@xps \
    --to=ps@pks.im \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.