From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-mirrorstats:master commit in: /
Date: Tue, 28 Apr 2020 16:46:44 +0000 (UTC) [thread overview]
Message-ID: <1588092352.34db670aff7f8da1eb1c90b7ad68cec526cfb4c6.robbat2@gentoo> (raw)
commit: 34db670aff7f8da1eb1c90b7ad68cec526cfb4c6
Author: Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 28 16:45:32 2020 +0000
Commit: Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
CommitDate: Tue Apr 28 16:45:52 2020 +0000
URL: https://gitweb.gentoo.org/proj/gentoo-mirrorstats.git/commit/?id=34db670a
probe-mirmon: fix rsync case
Signed-off-by: Robin H. Johnson <robbat2 <AT> gentoo.org>
probe-mirmon | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/probe-mirmon b/probe-mirmon
index 7b57923..ddd8546 100755
--- a/probe-mirmon
+++ b/probe-mirmon
@@ -17,6 +17,8 @@
main(@ARGV);
+use strict;
+use warnings;
use Date::Parse (); # dev-perl/TimeDate
use File::Tempdir; # dev-perl/File-Tempdir
@@ -56,19 +58,20 @@ sub handle_rsync {
exit 900; # rediculous exit code.
};
- print munge_date(<fh>);
+ print munge_date(<$fh>);
exit 0;
}
sub munge_date {
- my $timestr = $_;
+ no warnings 'numeric'; ## no critic (TestingAndDebugging::ProhibitNoWarnings)
+ my $timestr = shift;
my $timestamp = int($timestr);
my $year2020 = 1577836800;
my $year2038 = 2145916800;
# If the string starts with an epoch, just use that
- if($int_timestamp >= $year2020 && $int_timestamp <= $year2038) {
- return $int_timestamp;
+ if($timestamp >= $year2020 && $timestamp <= $year2038) {
+ return $timestamp;
} else {
return Date::Parse::str2time($timestr);
}
next reply other threads:[~2020-04-28 16:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 16:46 Robin H. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-22 17:44 [gentoo-commits] proj/gentoo-mirrorstats:master commit in: / Robin H. Johnson
2023-03-22 16:29 Robin H. Johnson
2023-03-22 16:29 Robin H. Johnson
2020-05-01 17:59 Robin H. Johnson
2020-04-30 22:59 Robin H. Johnson
2020-04-30 22:56 Robin H. Johnson
2020-04-30 22:56 Robin H. Johnson
2020-04-30 22:52 Robin H. Johnson
2020-04-30 22:17 Robin H. Johnson
2020-04-30 21:27 Robin H. Johnson
2020-04-30 21:27 Robin H. Johnson
2020-04-30 21:11 Robin H. Johnson
2020-04-30 20:29 Robin H. Johnson
2020-04-30 6:31 Robin H. Johnson
2020-04-30 6:02 Robin H. Johnson
2020-04-29 6:45 Robin H. Johnson
2020-04-29 6:39 Robin H. Johnson
2020-04-29 5:48 Robin H. Johnson
2020-04-29 5:41 Robin H. Johnson
2020-04-29 5:33 Robin H. Johnson
2020-04-29 5:20 Robin H. Johnson
2020-04-29 5:20 Robin H. Johnson
2020-04-29 5:20 Robin H. Johnson
2020-04-28 23:21 Robin H. Johnson
2020-04-28 23:21 Robin H. Johnson
2020-04-28 17:42 Robin H. Johnson
2020-04-28 17:34 Robin H. Johnson
2020-04-28 7:54 Robin H. Johnson
2018-12-15 18:57 Alec Warner
2016-11-05 18:02 Robin H. Johnson
2014-02-12 3:44 Jeremy Olexa
2013-08-28 2:28 Alec Warner
2013-08-27 9:08 Alec Warner
2012-12-25 17:22 Jeremy Olexa
2012-12-22 10:46 Jeremy Olexa
2012-09-18 16:17 Jeremy Olexa
2012-06-20 21:05 Jeremy Olexa
2012-02-24 18:45 Jeremy Olexa
2011-06-02 13:48 Jeremy Olexa
2011-05-19 15:09 Jeremy Olexa
2011-05-19 15:09 Jeremy Olexa
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=1588092352.34db670aff7f8da1eb1c90b7ad68cec526cfb4c6.robbat2@gentoo \
--to=robbat2@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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