From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub-2.02~beta1 happened
Date: Wed, 18 Dec 2013 23:43:29 -0600 [thread overview]
Message-ID: <52B28781.2030503@gmail.com> (raw)
In-Reply-To: <52B2513C.7070104@gmail.com>
Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. I've just uploaded 2.02~beta1. This also means that we're
> now in freeze. I'm willing to consider exceptions on case-by-case basis
> but it would be exceptions. The major points to do before release:
> - ARM64 loader.
> - Yeeloong 3A support needs some love.
> - XEN would probably need config adjustments.
> - XNU loader needs fixes.
> - NEWS needs contents.
> - Documentation.
> - Loads and loads of testing and some bugfixes.
There are a few warnings for rijndael.c with gcc 4.8.2. A couple of
them are pretty trivial. Others probably should be turned off with
-Wno-strict-aliasing. Do you want a patch?
If so, is the following acceptable?
#pragma GCC diagnostic ignored "-Wstrict-aliasing"
-- Bruce
next prev parent reply other threads:[~2013-12-19 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 1:51 grub-2.02~beta1 happened Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 5:43 ` Bruce Dubbs [this message]
2013-12-19 12:39 ` rijndael.c warning (was Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-23 22:25 ` Mike Gilbert
2013-12-24 15:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 6:38 ` grub-2.02~beta1 happened Andrey Borzenkov
2013-12-19 9:53 ` ext4 inline data (Re: grub-2.02~beta1 happened) Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 16:05 ` Andrey Borzenkov
2013-12-19 18:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-19 19:59 ` Important EHCI bugfix " Aleš Nesrsta
2013-12-20 12:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-20 17:57 ` Aleš Nesrsta
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=52B28781.2030503@gmail.com \
--to=bruce.dubbs@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).