From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 855b46da2f30f52ed4f852f19061df4913c4196b
Date: Thu, 07 Apr 2022 09:14:36 +0000 [thread overview]
Message-ID: <4KYwgd1KRbz2xgR@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1587 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 855b46da2f30f52ed4f852f19061df4913c4196b (commit)
from 3f65e4996b10f371129612f4b7e94beaa8ac3cb3 (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 855b46da2f30f52ed4f852f19061df4913c4196b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Apr 7 09:14:08 2022 +0000
core167: Ship coreutils
These have changed since they are now compiled with ACL/XATTR support
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/103 => core/167}/filelists/coreutils | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/103 => core/167}/filelists/coreutils (100%)
Difference in files:
diff --git a/config/rootfiles/core/167/filelists/coreutils b/config/rootfiles/core/167/filelists/coreutils
new file mode 120000
index 000000000..7351ed2cf
--- /dev/null
+++ b/config/rootfiles/core/167/filelists/coreutils
@@ -0,0 +1 @@
+../../../common/coreutils
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-04-07 9:14 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=4KYwgd1KRbz2xgR@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