From: Eli Schwartz <eschwartz@archlinux.org>
To: grub-devel@gnu.org
Subject: Re: [PATCH] btrfs: disable zstd support for i386-pc
Date: Thu, 11 Jun 2020 18:58:50 -0400 [thread overview]
Message-ID: <fd0473e6-c0be-d927-10b0-1f1bfa7b1b82@archlinux.org> (raw)
In-Reply-To: <CAEaD8JMMXS34MejD0QotKqUB98fzgODmn+Gs7xP5pc7NP+5EeA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]
On 11/7/19 12:08 AM, Vladimir 'phcoder' Serbinenko wrote:
> On Wed, 6 Nov 2019, 20:55 Michael Chang, <MChang@suse.com> wrote:
>
>> On Wed, Nov 06, 2019 at 11:15:04AM -0800, Vladimir 'phcoder' Serbinenko
>> wrote:
>>> Please don't do it this way. The right solution is to move it to separate
>>> module and include zstd module when needed.
>>
>> I fully agree to work out a proper solution, but before that I think it
>> is necessary to stop it from spread out going forward, as the running
>> system upgrading to new version could be affected and the consequence is
>> fatal - an unbootable system, qualified to be show stopper imho.
>>
> We don't do a release right now, so I don't think it's justified. Also
> increase in size can easily come from a compiler. If an increase in size
> can make system unbootable on upgrade, I'd rather be fixing this than just
> pepper over it.
Given grub 2.06 is on the horizon, is it time to re-evaluate this and
disable something known to be badly broken?
Failing that, is anyone working on making it a separate module? :)
--
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1601 bytes --]
next prev parent reply other threads:[~2020-06-11 23:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:19 [PATCH] btrfs: disable zstd support for i386-pc Michael Chang
2019-11-05 10:52 ` Paul Menzel
2019-11-07 4:22 ` Michael Chang
2019-11-06 12:40 ` David Sterba
2019-11-06 18:53 ` Nick Terrell
2019-11-07 6:34 ` Michael Chang
2019-11-06 19:15 ` Vladimir 'phcoder' Serbinenko
2019-11-07 4:55 ` Michael Chang
2019-11-07 5:08 ` Vladimir 'phcoder' Serbinenko
2019-11-07 6:59 ` Michael Chang
2020-06-11 22:58 ` Eli Schwartz [this message]
2020-06-21 18:26 ` Mike Gilbert
2020-06-21 18:56 ` Eli Schwartz
2020-06-23 1:59 ` Mike Gilbert
2020-06-23 2:16 ` Mike Gilbert
2020-06-23 6:32 ` Michael Chang
2020-06-23 17:50 ` Mike Gilbert
2019-11-07 11:52 ` Daniel Kiper
2019-11-13 11:00 ` Daniel Kiper
2019-11-14 9:53 ` Michael Chang
2019-11-15 11:42 ` Daniel Kiper
2019-11-19 8:34 ` Michael Chang
2020-03-03 16:59 ` Daniel Kiper
2020-03-04 7:58 ` Michael Chang
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=fd0473e6-c0be-d927-10b0-1f1bfa7b1b82@archlinux.org \
--to=eschwartz@archlinux.org \
--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.