From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5462658ea03ea86d5c093de3eb708d367aa077ac
Date: Sat, 12 Feb 2022 18:11:27 +0000 [thread overview]
Message-ID: <4Jwz7z4yJFz2xgg@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1597 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 5462658ea03ea86d5c093de3eb708d367aa077ac (commit)
from 5b0eca95280d4eca42d54b007f4fd41c33a82152 (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 5462658ea03ea86d5c093de3eb708d367aa077ac
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 12 18:06:39 2022 +0000
firewall: fix missing space
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/system/firewall | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/src/initscripts/system/firewall b/src/initscripts/system/firewall
index 577c10c89..48653ff57 100644
--- a/src/initscripts/system/firewall
+++ b/src/initscripts/system/firewall
@@ -7,7 +7,7 @@ eval $(/usr/local/bin/readhash /var/ipfire/ppp/settings)
eval $(/usr/local/bin/readhash /var/ipfire/ethernet/settings)
eval $(/usr/local/bin/readhash /var/ipfire/optionsfw/settings)
IFACE=`/bin/cat /var/ipfire/red/iface 2> /dev/null | /usr/bin/tr -d '\012'`
-if [ -z $IFACE]; then
+if [ -z $IFACE ]; then
IFACE="red0"
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-02-12 18:11 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=4Jwz7z4yJFz2xgg@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