From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b244d9b0d63f13f396c8a060767f9d86b96e9d5e
Date: Sun, 24 Jul 2022 10:23:42 +0000 [thread overview]
Message-ID: <4LrK5W0szxz2y0W@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1476 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 b244d9b0d63f13f396c8a060767f9d86b96e9d5e (commit)
from 901f6b7c292da9829a7ff4cf04caad48128bf87e (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 b244d9b0d63f13f396c8a060767f9d86b96e9d5e
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Sun Jul 24 10:23:17 2022 +0000
Core Update 170: Ship krb5
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/169 => core/170}/filelists/krb5 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/169 => core/170}/filelists/krb5 (100%)
Difference in files:
diff --git a/config/rootfiles/core/170/filelists/krb5 b/config/rootfiles/core/170/filelists/krb5
new file mode 120000
index 000000000..082c3cbcd
--- /dev/null
+++ b/config/rootfiles/core/170/filelists/krb5
@@ -0,0 +1 @@
+../../../common/krb5
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-07-24 10:23 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=4LrK5W0szxz2y0W@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