From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. ad9d6bf585c91e4696bdffbb3bf63ff741b09c81
Date: Tue, 22 Feb 2022 11:40:20 +0000 [thread overview]
Message-ID: <4K2y051XFYz2xf0@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via ad9d6bf585c91e4696bdffbb3bf63ff741b09c81 (commit)
from 3b45d9561b6d30d9491419a2022f2befaf2b2f4a (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit ad9d6bf585c91e4696bdffbb3bf63ff741b09c81
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Feb 22 11:38:15 2022 +0000
core164: exclude boot/uEnv.txt
uEnv.txt was destroyed on aarch64 because here a new u-boot was shipped.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/164/exclude | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/164/exclude b/config/rootfiles/core/164/exclude
index 818039f4a..b22e5e943 100644
--- a/config/rootfiles/core/164/exclude
+++ b/config/rootfiles/core/164/exclude
@@ -1,6 +1,7 @@
boot/config.txt
boot/grub/grub.cfg
boot/grub/grubenv
+boot/uEnv.txt
etc/alternatives
etc/collectd.custom
etc/default/grub
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-02-22 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4K2y051XFYz2xf0@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox