From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ad1204e4eb397b4f7d10c3bdfa9214aa8c0a0575
Date: Mon, 06 Nov 2017 19:08:35 +0000 [thread overview]
Message-ID: <20171106190835.A4C081081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1549 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 ad1204e4eb397b4f7d10c3bdfa9214aa8c0a0575 (commit)
from 5c8acc789b4756d942d5e465361eb6b8e3ebad4a (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 ad1204e4eb397b4f7d10c3bdfa9214aa8c0a0575
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Nov 6 19:07:10 2017 +0000
captive: One month is only 30 days instead of 210
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/captive.cgi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/html/cgi-bin/captive.cgi b/html/cgi-bin/captive.cgi
index 242549d..113c29f 100755
--- a/html/cgi-bin/captive.cgi
+++ b/html/cgi-bin/captive.cgi
@@ -42,7 +42,7 @@ my %session_times = (
86400 => $Lang::tr{'24 hours'},
604800 => $Lang::tr{'one week'},
1209600 => $Lang::tr{'two weeks'},
- 18144000 => $Lang::tr{'one month'},
+ 2592000 => $Lang::tr{'one month'},
31536000 => $Lang::tr{'one year'},
0 => "- $Lang::tr{'unlimited'} -",
);
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-11-06 19:08 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=20171106190835.A4C081081BCF@git01.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