From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 0f7a8e02c7ae3cfd6ab5612289a4c99bcadcdfe1
Date: Thu, 24 Sep 2020 14:14:57 +0000 [thread overview]
Message-ID: <4Bxxrd4dPjz2xc6@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1589 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 0f7a8e02c7ae3cfd6ab5612289a4c99bcadcdfe1 (commit)
from cf58f6593148f55b2016e2a18af75925271ef1b7 (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 0f7a8e02c7ae3cfd6ab5612289a4c99bcadcdfe1
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Sep 19 16:13:51 2020 +0000
index.cgi: Fix CPU architecture check
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/index.cgi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/html/cgi-bin/index.cgi b/html/cgi-bin/index.cgi
index 8e7207d0c..5aec4c594 100644
--- a/html/cgi-bin/index.cgi
+++ b/html/cgi-bin/index.cgi
@@ -547,7 +547,7 @@ if ( ! -e "/var/ipfire/main/send_profile") {
# Legacy architecture
my ($sysname, $nodename, $release, $version, $machine) = &POSIX::uname();
-if ($machine =~ m/^i?86$/) {
+if ($machine =~ m/^i.86$/) {
$warnmessage .= "<li>$Lang::tr{'legacy architecture warning'}</li>";
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-09-24 14:14 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=4Bxxrd4dPjz2xc6@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