From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Cc: Steve McIntyre <steve@einval.com>, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH] Remove HFS support
Date: Wed, 24 Aug 2022 09:16:06 +0200 [thread overview]
Message-ID: <a3491af3-dc28-f8df-f54f-0a5bd3b5b682@physik.fu-berlin.de> (raw)
In-Reply-To: <CADWks+ZFLj5vvOAZun42eK9wV7Ab++daPnFwDVpbiLh6NdSumg@mail.gmail.com>
Hello!
On 8/19/22 21:04, Dimitri John Ledkov wrote:
> There is no need for that code on any signed grubs or upstream. Ports that want to
> support this patch can have it conditionally compiled / enabled only on that arch,
> but not other.
That's not how open source works. Individual projects do not get to determine what
upstream software supports and what not. And that goes both ways.
> For example, in Ubuntu we already use separate builds for signed & unsigned bootloaders.
> Or one may keep grub-2.06 as separate source package. It's not like those old platforms
> need any new features in the bootloader ever again.
That's not the point. Packages are constantly rebuild in Debian for various reasons and
having to maintain the package manually in Debian is quite annoying.
Forcing older ports to use forks of upstream projects is an "elegant" way to kill of these
ports as the maintenance burn gets too high.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2022-08-24 7:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 13:38 [PATCH] Remove HFS support Daniel Axtens
2022-08-19 13:57 ` Daniel Kiper
2022-08-19 14:03 ` John Paul Adrian Glaubitz
2022-08-19 17:57 ` Vladimir 'phcoder' Serbinenko
2022-08-20 14:23 ` Daniel Axtens
2022-08-19 18:09 ` Steve McIntyre
2022-08-19 18:38 ` John Paul Adrian Glaubitz
2022-08-19 19:04 ` Dimitri John Ledkov
2022-08-19 19:45 ` Vladimir 'phcoder' Serbinenko
2022-08-20 14:05 ` Daniel Axtens
2022-08-24 7:17 ` John Paul Adrian Glaubitz
2022-08-24 7:16 ` John Paul Adrian Glaubitz [this message]
2022-08-20 14:13 ` Daniel Axtens
2022-08-19 19:01 ` Vladimir 'phcoder' Serbinenko
2022-08-26 15:46 ` John Paul Adrian Glaubitz
2022-08-26 17:02 ` Vladimir 'phcoder' Serbinenko
2022-08-20 13:53 ` Daniel Axtens
2022-08-24 7:21 ` John Paul Adrian Glaubitz
2022-08-26 13:31 ` Daniel Axtens
2022-08-26 15:17 ` Vladimir 'phcoder' Serbinenko
2022-08-30 18:28 ` Robbie Harwood
2022-09-01 14:01 ` Daniel Axtens
2022-08-26 15:27 ` John Paul Adrian Glaubitz
2022-08-30 16:37 ` Robbie Harwood
2022-08-30 17:21 ` John Paul Adrian Glaubitz
2022-08-30 18:43 ` Robbie Harwood
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=a3491af3-dc28-f8df-f54f-0a5bd3b5b682@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dimitri.ledkov@canonical.com \
--cc=dja@axtens.net \
--cc=grub-devel@gnu.org \
--cc=steve@einval.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.