From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 107060da53570e15281a173365a9e56149171d41
Date: Mon, 28 Apr 2014 18:25:44 +0200 [thread overview]
Message-ID: <20140428162544.D0488212B3@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1726 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 107060da53570e15281a173365a9e56149171d41 (commit)
from a43c9b6a64cd47e55399c319c44fd452d8056e03 (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 107060da53570e15281a173365a9e56149171d41
Author: Alexander Marx <alexander.marx(a)ipfire.org>
Date: Mon Apr 28 14:55:22 2014 +0200
Firewall: When using DNAT AUTO, don't display the IP anymore in brackets
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/firewall.cgi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/firewall.cgi b/html/cgi-bin/firewall.cgi
index ff950c4..48e3a8d 100644
--- a/html/cgi-bin/firewall.cgi
+++ b/html/cgi-bin/firewall.cgi
@@ -2562,11 +2562,11 @@ END
push (@nat_ifaces,&fwlib::get_nat_address($$hash{$key}[29],$val));
}
@nat_ifaces=&del_double(@nat_ifaces);
- $natstring = join(', ', @nat_ifaces);
+ $natstring = "";
}else{
- $natstring = $$hash{$key}[29];
+ $natstring = "($$hash{$key}[29])";
}
- print "$Lang::tr{'firewall'} ($natstring)";
+ print "$Lang::tr{'firewall'} $natstring";
if($$hash{$key}[30] ne ''){
$$hash{$key}[30]=~ tr/|/,/;
print": $$hash{$key}[30]";
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-04-28 16:25 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=20140428162544.D0488212B3@argus.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