From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 4/4] graphs.pl: use brackets instead of hypens
Date: Mon, 27 Apr 2020 17:25:15 +0200 [thread overview]
Message-ID: <e822b5c2-a962-255d-d491-2ef586adbd3a@ipfire.org> (raw)
In-Reply-To: <d88729dd-6ed0-a519-ffbe-f6f80a756d45@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
This simply makes more sense in most languages, as INPUT, OUTPUT and
FORWARD are special cases of firewall hits in general.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/cfgroot/graphs.pl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/config/cfgroot/graphs.pl b/config/cfgroot/graphs.pl
index 872e9bd7c..7b056d117 100644
--- a/config/cfgroot/graphs.pl
+++ b/config/cfgroot/graphs.pl
@@ -683,17 +683,17 @@ sub updatefwhitsgraph {
"COMMENT:".sprintf("%15s",$Lang::tr{'average'}),
"COMMENT:".sprintf("%14s",$Lang::tr{'minimal'}),
"COMMENT:".sprintf("%15s",$Lang::tr{'current'})."\\j",
- "AREA:output".$color{"color25"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}."-OUTPUT"),
+ "AREA:output".$color{"color25"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}." (OUTPUT)"),
"GPRINT:output:MAX:%8.1lf %sBps",
"GPRINT:output:AVERAGE:%8.1lf %sBps",
"GPRINT:output:MIN:%8.1lf %sBps",
"GPRINT:output:LAST:%8.1lf %sBps\\j",
- "STACK:forward".$color{"color23"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}."-FORWARD"),
+ "STACK:forward".$color{"color23"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}." (FORWARD)"),
"GPRINT:forward:MAX:%8.1lf %sBps",
"GPRINT:forward:AVERAGE:%8.1lf %sBps",
"GPRINT:forward:MIN:%8.1lf %sBps",
"GPRINT:forward:LAST:%8.1lf %sBps\\j",
- "STACK:input".$color{"color24"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}."-INPUT"),
+ "STACK:input".$color{"color24"}."A0:".sprintf("%-25s",$Lang::tr{'firewallhits'}." (INPUT)"),
"GPRINT:input:MAX:%8.1lf %sBps",
"GPRINT:input:AVERAGE:%8.1lf %sBps",
"GPRINT:input:MIN:%8.1lf %sBps",
--
2.16.4
next prev parent reply other threads:[~2020-04-27 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 15:24 [PATCH 1/4] graphs.pl: fix spelling of "SYN" Peter Müller
2020-04-27 15:24 ` [PATCH 2/4] en.pl: " Peter Müller
2020-04-27 15:24 ` [PATCH 3/4] de.pl: mention technical detail regarding new not SYN packets Peter Müller
2020-04-27 15:25 ` Peter Müller [this message]
2020-04-27 15:33 ` [PATCH 4/4] graphs.pl: use brackets instead of hypens Michael Tremer
2020-04-27 15:33 ` [PATCH 3/4] de.pl: mention technical detail regarding new not SYN packets Michael Tremer
2020-04-27 15:33 ` [PATCH 2/4] en.pl: fix spelling of "SYN" Michael Tremer
2020-04-27 15:33 ` [PATCH 1/4] graphs.pl: " Michael Tremer
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=e822b5c2-a962-255d-d491-2ef586adbd3a@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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