From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Gummiboot fixup
Date: Tue, 19 Mar 2019 19:56:19 +0100 [thread overview]
Message-ID: <875zseitgs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190319112852.9592-1-esben.haabendal@gmail.com> (Esben Haabendal's message of "Tue, 19 Mar 2019 12:28:49 +0100")
>>>>> "Esben" == Esben Haabendal <esben.haabendal@gmail.com> writes:
> From: Esben Haabendal <esben@haabendal.dk>
> These patches fixes gummiboot for building with toolchains using
> newer gcc and glibc versions.
> Esben Haabendal (3):
> gummiboot: use new official upstream git repository
> gummiboot: upgrade to last commit before being removed
> gummiboot: fix compatibility with newer glibc versions
Out of interest, what is the use case for using gummiboot? We recently
added systemd-boot support, so I was considering removing gummiboot as
it is dead upstream.
Notice that you currently cannot enable systemd-boot without the rest of
systemd, so that may be a disadvantage.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-19 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 11:28 [Buildroot] [PATCH 0/3] Gummiboot fixup Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 1/3] gummiboot: use new official upstream git repository Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 2/3] gummiboot: upgrade to last commit before being removed Esben Haabendal
2019-03-19 11:28 ` [Buildroot] [PATCH 3/3] gummiboot: fix compatibility with newer glibc versions Esben Haabendal
2019-03-19 21:02 ` Thomas Petazzoni
2019-03-19 18:56 ` Peter Korsgaard [this message]
[not found] ` <CAOR3GqXSxZw3m+OD3FLCFOR0Gi-v3zNJGe2+3Bhy7R6av7LVhQ@mail.gmail.com>
2019-03-20 13:46 ` [Buildroot] [PATCH 0/3] Gummiboot fixup Peter Korsgaard
[not found] ` <CAOR3GqU17TUskOwG_8DfwrcEt_AJcqzgD8=5j1c2Wa+LVveeSg@mail.gmail.com>
2019-03-20 14:36 ` Peter Korsgaard
2019-03-20 15:03 ` Esben Haabendal
2019-03-20 16:30 ` Peter Korsgaard
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=875zseitgs.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.