All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Watson <cjwatson@debian.org>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: mchang@suse.com, grub-devel@gnu.org,
	Marco A Benatto <mbenatto@redhat.com>,
	Javier Martinez Canillas <javierm@redhat.com>
Subject: Re: [PATCH v2] i386-pc: build verifiers API as module
Date: Mon, 22 Mar 2021 16:16:26 +0000	[thread overview]
Message-ID: <20210322161626.GN26923@riva.ucam.org> (raw)
In-Reply-To: <20210322152000.ebheegnkkhpqa4d3@tomti.i.net-space.pl>

On Mon, Mar 22, 2021 at 04:20:00PM +0100, Daniel Kiper wrote:
> NAK for this patch and others "fixing" small MBR gaps. I am not going to
> deal with this kind of issues any longer because a few folks in the
> world cannot/do not want/... reinstall their systems. Sorry guys.

I'd just like to say that I think this is an unfortunate mistake, and
puts distributions in an invidious position.

> Additionally, the commit 5fd18f77e (mbr: Warn if MBR gap is small and
> user uses advanced modules) and 505d92f5e (mbr: Document new limitations
> on MBR gap support) are pretty clear we do not support advanced configs
> with small MBR gaps any longer.

Yes.  As I recently posted to the list, I do not think this should be
used as an excuse not to fix problems where it is relatively
straightforward to do so.

-- 
Colin Watson (he/him)                              [cjwatson@debian.org]


  reply	other threads:[~2021-03-22 16:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 11:30 [PATCH v2] i386-pc: build verifiers API as module Michael Chang
2021-03-22 15:20 ` Daniel Kiper
2021-03-22 16:16   ` Colin Watson [this message]
2021-03-22 20:09     ` Colin Watson
2021-03-22 20:19     ` Glenn Washburn
2021-03-22 20:45       ` Colin Watson
2021-03-23 16:33         ` Daniel Kiper
2021-03-23 17:45           ` Lennart Sorensen
2021-03-24  4:44           ` Michael Chang
2021-03-26 17:01             ` Daniel Kiper
2021-04-12 13:15               ` Daniel Kiper
2021-04-13  4:13                 ` Michael Chang
2021-04-14 13:22                   ` Daniel Kiper
2021-04-16 21:23                     ` Colin Watson
2021-04-20  3:49                     ` Michael Chang
2021-04-28 13:45                       ` Daniel Kiper
2021-03-22 21:43       ` James Bottomley
2021-03-23  4:16   ` Michael Chang
2021-03-23 11:37     ` Javier Martinez Canillas
2021-03-23 13:27       ` Colin Watson
2021-03-23 14:26         ` Javier Martinez Canillas
2021-03-23 17:26         ` Daniel Kiper
2021-03-23 16:48     ` Daniel Kiper
2021-03-24  3:50       ` Michael Chang
2021-03-26 17:22         ` Daniel Kiper
2021-08-22 19:50 Michael Schierl
2021-08-22 20:23 ` Didier Spaier

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=20210322161626.GN26923@riva.ucam.org \
    --to=cjwatson@debian.org \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=javierm@redhat.com \
    --cc=mbenatto@redhat.com \
    --cc=mchang@suse.com \
    /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.