From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 99c7fefd7ecf2404b7b938bff1002679c1fb58e5
Date: Mon, 17 Jan 2022 13:28:05 +0000 [thread overview]
Message-ID: <4Jct520Mx3z2xZm@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1563 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, master has been updated
via 99c7fefd7ecf2404b7b938bff1002679c1fb58e5 (commit)
from 43adf2dce9b35a11fc3b947c87466aef29176159 (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 99c7fefd7ecf2404b7b938bff1002679c1fb58e5
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jan 17 13:26:08 2022 +0000
core163: add missing core-files
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/159 => core/163}/filelists/core-files | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/159 => core/163}/filelists/core-files (100%)
Difference in files:
diff --git a/config/rootfiles/core/163/filelists/core-files b/config/rootfiles/core/163/filelists/core-files
new file mode 100644
index 000000000..f196f54d8
--- /dev/null
+++ b/config/rootfiles/core/163/filelists/core-files
@@ -0,0 +1,5 @@
+etc/issue
+etc/os-release
+etc/system-release
+srv/web/ipfire/cgi-bin/credits.cgi
+var/ipfire/langs
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-01-17 13: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=4Jct520Mx3z2xZm@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