From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c14203248c2a36d504af122c8ab5185346c65166
Date: Sat, 06 Sep 2014 18:45:09 +0200 [thread overview]
Message-ID: <20140906164509.80128210AA@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1511 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 c14203248c2a36d504af122c8ab5185346c65166 (commit)
from da05e07629a8d1afccdb356ac47964df41987476 (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 c14203248c2a36d504af122c8ab5185346c65166
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Sep 6 18:44:50 2014 +0200
general-functions.pl: Fix perl coding error
-----------------------------------------------------------------------
Summary of changes:
config/cfgroot/general-functions.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/cfgroot/general-functions.pl b/config/cfgroot/general-functions.pl
index 4ed5a55..35ae7c0 100644
--- a/config/cfgroot/general-functions.pl
+++ b/config/cfgroot/general-functions.pl
@@ -286,7 +286,7 @@ sub validip
sub validmask {
my $mask = shift;
- return &Network::check_netmask($mask) or &Network::check_prefix($mask);
+ return &Network::check_netmask($mask) || &Network::check_prefix($mask);
}
sub validipormask
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-09-06 16:45 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=20140906164509.80128210AA@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