From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d95af1ad4a5aeb7c2ce7b71d1e392c6355013db6
Date: Mon, 30 Dec 2024 18:03:10 +0000 [thread overview]
Message-ID: <4YMP8t1L8Sz2y1N@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1541 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, next has been updated
via d95af1ad4a5aeb7c2ce7b71d1e392c6355013db6 (commit)
from 4bd8107bf940d5cbcb7ed0b7ddfe13f76190549f (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 d95af1ad4a5aeb7c2ce7b71d1e392c6355013db6
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Dec 30 19:02:26 2024 +0100
core192: ship u-boot for aarch64
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/159 => core/192}/filelists/aarch64/u-boot | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/159 => core/192}/filelists/aarch64/u-boot (100%)
Difference in files:
diff --git a/config/rootfiles/core/192/filelists/aarch64/u-boot b/config/rootfiles/core/192/filelists/aarch64/u-boot
new file mode 120000
index 0000000000..2a16bdbfe2
--- /dev/null
+++ b/config/rootfiles/core/192/filelists/aarch64/u-boot
@@ -0,0 +1 @@
+../../../../common/aarch64/u-boot
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2024-12-30 18:03 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=4YMP8t1L8Sz2y1N@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