From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 572249bbf385d09dad98d0359921f96220a87c9f
Date: Sun, 24 Oct 2021 12:13:42 +0000 [thread overview]
Message-ID: <4HccSQ4Wsdz2y8g@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1489 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 572249bbf385d09dad98d0359921f96220a87c9f (commit)
from 05b6dd44bef2f8a2cc4827533a6ff070a8852b8e (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 572249bbf385d09dad98d0359921f96220a87c9f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Oct 24 12:13:20 2021 +0000
core161: add iproute2
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/106 => core/161}/filelists/iproute2 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/106 => core/161}/filelists/iproute2 (100%)
Difference in files:
diff --git a/config/rootfiles/core/161/filelists/iproute2 b/config/rootfiles/core/161/filelists/iproute2
new file mode 120000
index 000000000..05f0f71fb
--- /dev/null
+++ b/config/rootfiles/core/161/filelists/iproute2
@@ -0,0 +1 @@
+../../../common/iproute2
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-10-24 12:13 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=4HccSQ4Wsdz2y8g@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