From: Matt Turner <mattst88@gmail.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
The development of GNU GRUB <grub-devel@gnu.org>,
Mike Gilbert <floppym@gentoo.org>
Subject: Re: GRUB 2.06 release
Date: Fri, 28 Feb 2020 10:26:17 -0800 [thread overview]
Message-ID: <CAEdQ38Gx3SsToAUkceReZYiC357Zd7x0VC=cGBaqrfCoeRRJ-g@mail.gmail.com> (raw)
In-Reply-To: <20200228124619.bez2m3e5gggumv5s@tomti.i.net-space.pl>
On Fri, Feb 28, 2020 at 4:46 AM Daniel Kiper <dkiper@net-space.pl> wrote:
>
> On Tue, Feb 25, 2020 at 02:15:16PM +0100, John Paul Adrian Glaubitz wrote:
> > Hi!
> >
> > On 2/20/20 9:46 AM, John Paul Adrian Glaubitz wrote:
> > > On 2/19/20 4:01 PM, Daniel Kiper wrote:
> > >> As I told during my FOSDEM 2020 presentation we are preparing for
> > >> GRUB 2.06 release. Tentative schedule is below:
> > >> - code freeze: 15th of March, 23:59:59 UTC; everything posted after
> > >> that date will not be considered as a release material,
> > >> - release: taking into account last experience I think that it will
> > >> happen no later than June; hopefully earlier; exact date depends
> > >> on number of bugs found, etc.
> > >>
> > >> So, please plan accordingly...
> > >
> > > Let me know when you want me to start the build tests on all architectures.
> >
> > FWIW, it would be great if both these fixes could be included in the 2.06 release:
> >
> > * build: Disable PIE in TARGET_CCASFLAGS if needed
> > * build: Move TARGET_* assignments earlier
>
> All are in right now...
>
> Matt, Mike, I added SOB on behalf of you. I hope this is not a problem for you.
Thank you, Daniel. That's perfectly okay with me.
next prev parent reply other threads:[~2020-02-28 18:26 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 [this message]
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
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='CAEdQ38Gx3SsToAUkceReZYiC357Zd7x0VC=cGBaqrfCoeRRJ-g@mail.gmail.com' \
--to=mattst88@gmail.com \
--cc=dkiper@net-space.pl \
--cc=floppym@gentoo.org \
--cc=glaubitz@physik.fu-berlin.de \
--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.