| commit | 2ef18738d0c0ead317a7b04d9ee53e3d2a26638c | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Tue, 7 Jan 2020 01:33:53 +0000 (6 18:33 -0700) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Tue, 7 Jan 2020 01:33:53 +0000 (6 18:33 -0700) | ||
| tree | d3b13b9417829a6002a0719149e5f02797fcdec0 | treesnapshot (tar.gz zip) |
| parent | 991e398ad6f4975d6c85bd10fa8a4cc06074302c | commitdiff |
gitweb: avoid bizarre Time::Local year interpretation
While both gmtime and localtime return a "year - 1900" value for
the year, if that resulting "year - 1900" value ends up being in
the range 0..99 inclusive it will be misinterpreted by the
Time::Local timegm and timelocal functions.
Avoid this problem by always converting from a "year - 1900" value
to an actual year value before passing to Time::Local functions.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
While both gmtime and localtime return a "year - 1900" value for
the year, if that resulting "year - 1900" value ends up being in
the range 0..99 inclusive it will be misinterpreted by the
Time::Local timegm and timelocal functions.
Avoid this problem by always converting from a "year - 1900" value
to an actual year value before passing to Time::Local functions.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| gitweb/gitweb.perl | diffblobblamehistory |