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. 675849974918df21c717c26bf6e974fa2f9d7f67
Date: Thu, 12 May 2022 17:28:39 +0000 [thread overview]
Message-ID: <4KzdzX3FRfz2xjD@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1620 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 675849974918df21c717c26bf6e974fa2f9d7f67 (commit)
from 91f1aaaa869df6fe9a04d3aefb36f021e9945ad7 (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 675849974918df21c717c26bf6e974fa2f9d7f67
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Thu May 12 17:27:34 2022 +0000
Core Update 168: Ship core-files
https://community.ipfire.org/t/core-168-testing-working/7901/7
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/168/{ => filelists}/core-files | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/core/168/{ => filelists}/core-files (100%)
Difference in files:
diff --git a/config/rootfiles/core/168/filelists/core-files b/config/rootfiles/core/168/filelists/core-files
new file mode 100644
index 000000000..0dec37e53
--- /dev/null
+++ b/config/rootfiles/core/168/filelists/core-files
@@ -0,0 +1,5 @@
+etc/system-release
+etc/issue
+etc/os-release
+srv/web/ipfire/cgi-bin/credits.cgi
+var/ipfire/langs
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-05-12 17:28 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=4KzdzX3FRfz2xjD@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