From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 77a942d735713f3117f967f9995c0e7ca6d68d14
Date: Tue, 11 Feb 2025 09:16:38 +0000 [thread overview]
Message-ID: <4YsbRV2LVTz2xMv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 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 77a942d735713f3117f967f9995c0e7ca6d68d14 (commit)
from 9ad59410624beaccef5c75bcca4e1d4ddb0be98b (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 77a942d735713f3117f967f9995c0e7ca6d68d14
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Feb 11 10:15:44 2025 +0100
core192: ship libyang
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/164 => core/192}/filelists/libyang | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/164 => core/192}/filelists/libyang (100%)
Difference in files:
diff --git a/config/rootfiles/core/192/filelists/libyang b/config/rootfiles/core/192/filelists/libyang
new file mode 120000
index 000000000..50c26d048
--- /dev/null
+++ b/config/rootfiles/core/192/filelists/libyang
@@ -0,0 +1 @@
+../../../common/libyang
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-02-11 9:16 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=4YsbRV2LVTz2xMv@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