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. b630a9a8a8dab5e558c0929191ee25da2e9d5068
Date: Wed, 18 May 2022 17:42:55 +0000 [thread overview]
Message-ID: <4L3L1D1m3Jz2xnY@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 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 b630a9a8a8dab5e558c0929191ee25da2e9d5068 (commit)
from 1c1d9fd7bfdf5495069c3119982753a9ddc5fe24 (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 b630a9a8a8dab5e558c0929191ee25da2e9d5068
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Wed May 18 17:42:24 2022 +0000
Core Update 168: fcrontab != crontab
Silly me.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/168/filelists/files | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/168/filelists/files b/config/rootfiles/core/168/filelists/files
index 159d43d86..5f5e172df 100644
--- a/config/rootfiles/core/168/filelists/files
+++ b/config/rootfiles/core/168/filelists/files
@@ -391,7 +391,6 @@ lib/firmware/rtw88/rtw8821c_fw.bin
lib/firmware/rtw88/rtw8822c_fw.bin
lib/firmware/rtw89/rtw8852a_fw.bin
lib/firmware/wfx/wfm_wf200_C0.sec
-usr/bin/fcrontab
usr/lib/firewall/rules.pl
usr/local/bin/update-ids-ruleset
usr/sbin/convert-ids-backend-files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-05-18 17:42 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=4L3L1D1m3Jz2xnY@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