From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9da0695da76e008fbfadbf976b5eaa904f707b40
Date: Fri, 10 Feb 2012 11:11:56 +0100 [thread overview]
Message-ID: <20120210101157.3BAFA200BF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1735 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 9da0695da76e008fbfadbf976b5eaa904f707b40 (commit)
from a73f60abb870bf94498eb1147f97b7b67b036f32 (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 9da0695da76e008fbfadbf976b5eaa904f707b40
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Feb 10 11:10:14 2012 +0100
outgoingfw.cgi: Fix enabled checkbox when editing rules.
When a rule was edited, the enabled checkbox was always unchecked.
References bug #10022.
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/outgoingfw.cgi | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/outgoingfw.cgi b/html/cgi-bin/outgoingfw.cgi
index 295bde4..b417817 100644
--- a/html/cgi-bin/outgoingfw.cgi
+++ b/html/cgi-bin/outgoingfw.cgi
@@ -631,7 +631,7 @@ END
sub addrule
{
&Header::openbox('100%', 'center', $Lang::tr{'Add Rule'});
- if ($outfwsettings{'EDIT'} eq 'no') { $selected{'ENABLED'} = 'checked'; }
+ if ($outfwsettings{'ENABLED'} eq 'on') { $selected{'ENABLED'} = 'checked'; }
$selected{'TIME_FROM'}{$outfwsettings{'TIME_FROM'}} = "selected='selected'";
$selected{'TIME_TO'}{$outfwsettings{'TIME_TO'}} = "selected='selected'";
print <<END
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-02-10 10: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=20120210101157.3BAFA200BF@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