From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 68530-done@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: bug#68530: [PATCH v2] gnu: u-boot: Update to 2024.01.
Date: Thu, 18 Jan 2024 10:23:04 -0800 [thread overview]
Message-ID: <875xzqbiwn.fsf@wireframe> (raw)
In-Reply-To: <878r4mbjac.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On 2024-01-18, Vagrant Cascadian wrote:
> * gnu/packages/bootloaders.scm (u-boot): Update to 2024.01.
> [source]: Remove patman patch, add build-without-libcrypto patch.
> * gnu/packages/patches/u-boot-allow-disabling-openssl.patch: Remove
> upstreamed diffs.
> * gnu/packages/patches/u-boot-build-without-libcrypto.patch: Add file.
> * gnu/packages/patches/u-boot-patman-change-id.patch: Delete file.
> * gnu/local.mk (dist_patch_DATA): Add patch, remove patch.
>
> I think I like that better! Opinions are likely to vary.
>
> That said, everything seems to build fine; I am inclined to push these
> changes! :)
Pushed as 3e3975275bbab84d58f7740e9680b265769aa580.
Thanks!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2024-01-18 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:47 [bug#68530] [PATCH 1/2] gnu: u-boot: Update to 2024.01.3 Herman Rimm via Guix-patches via
2024-01-17 13:59 ` [bug#68530] [PATCH 2/2] gnu: Add u-boot-amlogic Herman Rimm via Guix-patches via
2024-01-17 19:13 ` Vagrant Cascadian
2024-01-17 19:59 ` [bug#68530] [PATCH 1/2] gnu: u-boot: Update to 2024.01.3 Vagrant Cascadian
2024-01-18 16:03 ` Herman Rimm via Guix-patches via
2024-01-18 16:11 ` [bug#68530] [PATCH v2] gnu: u-boot: Update to 2024.01 Herman Rimm via Guix-patches via
2024-01-18 18:14 ` Vagrant Cascadian
2024-01-18 18:23 ` Vagrant Cascadian [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xzqbiwn.fsf@wireframe \
--to=vagrant@debian.org \
--cc=68530-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).