From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1b68fc29b4df4880ca4761cdb036d1b6aac8ab65
Date: Tue, 25 Feb 2020 06:41:37 +0000 [thread overview]
Message-ID: <48RTqP6YJyz2xtH@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1660 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 1b68fc29b4df4880ca4761cdb036d1b6aac8ab65 (commit)
from 712425ff0bbe96700de5a1b865d58730ba9c6b90 (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 1b68fc29b4df4880ca4761cdb036d1b6aac8ab65
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Feb 25 06:41:14 2020 +0000
core142: fix typo
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/142/filelists/files | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/142/filelists/files b/config/rootfiles/core/142/filelists/files
index 69d6eb7bc..4d6c69adb 100644
--- a/config/rootfiles/core/142/filelists/files
+++ b/config/rootfiles/core/142/filelists/files
@@ -9,7 +9,7 @@ lib/udev/network-hotplug-bridges
opt/pakfire/etc/pakfire.conf
opt/pakfire/lib/functions.pl
srv/web/ipfire/cgi-bin/dns.cgi
-srv/web/ipfire/cgi-bin/fireingo.cgi
+srv/web/ipfire/cgi-bin/fireinfo.cgi
srv/web/ipfire/cgi-bin/pakfire.cgi
srv/web/ipfire/cgi-bin/proxy.cgi
var/ipfire/suricata/ruleset-sources
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-02-25 6:41 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=48RTqP6YJyz2xtH@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