)]}' { "log": [ { "commit": "9fb22a3ec4ec5217fc29bb3ee3a0f1076098151f", "tree": "f5dabc7347b8aaa83675e4468edbccc657ae2fca", "parents": [ "cc56abbb007e090b830f510df6cb300ae12e1a89" ], "author": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Wed Oct 07 17:13:40 2015 -0700" }, "committer": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Fri Oct 09 15:15:39 2015 -0700" }, "message": "Sync with upstream tzcode (2015g).\n\nThis is quite a large patch because we haven\u0027t updated for some time,\nbut the good news is that upstream is now thread-safe so a lot of our\nchanges go away in this update and the remaining diff is a lot smaller.\n\n(Note that our whitespace still doesn\u0027t match upstream. I use diff -wub\nto compare. Upstream doesn\u0027t even really have a consistent style. New\ncode seems to be two spaces, old code tabs.)\n\nFrom the intervening changelogs (eliding the changes that only affected\nthe tools, which we don\u0027t use):\n\n2014a:\n An uninitialized-storage bug in \u0027localtime\u0027 has been fixed.\n (Thanks to Logan Chien.)\n\n2014b:\n \u0027zic\u0027 and \u0027localtime\u0027 no longer reject locations needing four\n transitions per year for the forseeable future. (Thanks to Andrew\n Main (Zefram).)\n\n2014c:\n \u003cNone\u003e\n\n2014d:\n \u003cNone\u003e\n\n2014e:\n \u003cNone\u003e\n\n2014f:\n \u0027localtime\u0027, \u0027mktime\u0027, etc. now use much less stack space if\n ALL_STATE is defined. (Thanks to Elliott Hughes for reporting the\n problem.)\n\n Some lint has been removed when using GCC_DEBUG_FLAGS with GCC\n 4.9.0.\n\n2014g:\n Unless NETBSD_INSPIRED is defined to 0, the tz library now\n supplies functions for creating and using objects that represent\n time zones. The new functions are tzalloc, tzfree, localtime_rz,\n mktime_z, and (if STD_INSPIRED is also defined) posix2time_z and\n time2posix_z. They are intended for performance: for example,\n localtime_rz (unlike localtime_r) is trivially thread-safe without\n locking. (Thanks to Christos Zoulas for proposing NetBSD-inspired\n functions, and to Alan Barrett and Jonathan Lennox for helping to\n debug the change.)\n\n If THREAD_SAFE is defined to 1, the tz library is now thread-safe.\n Although not needed for tz\u0027s own applications, which are single-threaded,\n this supports POSIX better if the tz library is used in multithreaded apps.\n\n Some crashes have been fixed when zdump or the tz library is given\n invalid or outlandish input.\n\n The tz library no longer mishandles leap seconds on platforms with\n unsigned time_t in time zones that lack ordinary transitions after 1970.\n\n The tz code now attempts to infer TM_GMTOFF and TM_ZONE if not\n already defined, to make it easier to configure on common platforms.\n Define NO_TM_GMTOFF and NO_TM_ZONE to suppress this.\n\n Unless the new macro UNINIT_TRAP is defined to 1, the tz code now\n assumes that reading uninitialized memory yields garbage values\n but does not cause other problems such as traps.\n\n If TM_GMTOFF is defined and UNINIT_TRAP is 0, mktime is now\n more likely to guess right for ambiguous time stamps near\n transitions where tm_isdst does not change.\n\n If HAVE_STRFTIME_L is defined to 1, the tz library now defines\n strftime_l for compatibility with recent versions of POSIX.\n Only the C locale is supported, though. HAVE_STRFTIME_L defaults\n to 1 on recent POSIX versions, and to 0 otherwise.\n\n tzselect -c now uses a hybrid distance measure that works better\n in Africa. (Thanks to Alan Barrett for noting the problem.)\n\n The C source code now ports to NetBSD when GCC_DEBUG_FLAGS is used,\n or when time_tz is defined.\n\n When HAVE_UTMPX_H is set the \u0027date\u0027 command now builds on systems\n whose \u003cutmpx.h\u003e file does not define WTMPX_FILE, and when setting\n the date it updates the wtmpx file if _PATH_WTMPX is defined.\n This affects GNU/Linux and similar systems.\n\n For easier maintenance later, some C code has been simplified,\n some lint has been removed, and the code has been tweaked so that\n plain \u0027make\u0027 is more likely to work.\n\n The C type \u0027bool\u0027 is now used for boolean values, instead of \u0027int\u0027.\n\n The long-obsolete LOCALE_HOME code has been removed.\n\n The long-obsolete \u0027gtime\u0027 function has been removed.\n\n2014h:\n The tz library\u0027s localtime and mktime functions now set tzname to a value\n appropriate for the requested time stamp, and zdump now uses this\n on platforms not defining TM_ZONE, fixing a 2014g regression.\n (Thanks to Tim Parenti for reporting the problem.)\n\n The tz library no longer sets tzname if localtime or mktime fails.\n\n An access to uninitalized data has been fixed.\n (Thanks to Jörg Richter for reporting the problem.)\n\n When THREAD_SAFE is defined, the code ports to the C11 memory model.\n A memory leak has been fixed if ALL_STATE and THREAD_SAFE are defined\n and two threads race to initialize data used by gmtime-like functions.\n (Thanks to Andy Heninger for reporting the problems.)\n\n2014i:\n The time-related library functions now set errno on failure,\n and some crashes in the new tzalloc-related library functions\n have been fixed. (Thanks to Christos Zoulas for reporting\n most of these problems and for suggesting fixes.)\n\n If USG_COMPAT is defined and the requested time stamp is\n standard time, the tz library\u0027s localtime and mktime functions\n now set the extern variable timezone to a value appropriate\n for that time stamp; and similarly for ALTZONE, daylight\n saving time, and the altzone variable. This change is a\n companion to the tzname change in 2014h, and is designed to\n make timezone and altzone more compatible with tzname.\n\n The tz library\u0027s functions now set errno to EOVERFLOW if they\n fail because the result cannot be represented. ctime and\n ctime_r now return NULL and set errno when a time stamp is out\n of range, rather than having undefined behavior.\n\n Some bugs associated with the new 2014g functions have been\n fixed. This includes a bug that largely incapacitated the new\n functions time2posix_z and posix2time_z. (Thanks to Christos\n Zoulas.) It also includes some uses of uninitialized\n variables after tzalloc. The new code uses the standard type\n \u0027ssize_t\u0027, which the Makefile now gives porting advice about.\n\n2014j:\n \u003cNone\u003e\n\n2015a:\n tzalloc now scrubs time zone abbreviations compatibly with the way\n that tzset always has, by replacing invalid bytes with \u0027_\u0027 and by\n shortening too-long abbreviations.\n\n2015b:\n Fix integer overflow bug in reference \u0027mktime\u0027 implementation.\n (Problem reported by Jörg Richter.)\n\n Allow -Dtime_tz\u003dtime_t compilations, and allow -Dtime_tz\u003d... libraries\n to be used in the same executable as standard-library time_t functions.\n (Problems reported by Bradley White.)\n\n2015c:\n \u003cNone\u003e\n\n2015d:\n \u003cNone\u003e\n\n2015e:\n \u003cNone\u003e\n\n2015f:\n \u003cNone\u003e\n\n2015g:\n localtime no longer mishandles America/Anchorage after 2037.\n (Thanks to Bradley White for reporting the bug.)\n\n On hosts with signed 32-bit time_t, localtime no longer mishandles\n Pacific/Fiji after 2038-01-16 14:00 UTC.\n\n The localtime module allows the variables \u0027timezone\u0027, \u0027daylight\u0027,\n and \u0027altzone\u0027 to be in common storage shared with other modules,\n and declares them in case the system \u003ctime.h\u003e does not.\n (Problems reported by Kees Dekker.)\n\n On platforms with tm_zone, strftime.c now assumes it is not NULL.\n This simplifies the code and is consistent with zdump.c.\n (Problem reported by Christos Zoulas.)\n\nChange-Id: I9eb0a8323cb8bd9968fcfe612dc14f45aa3b59d2\n" }, { "commit": "e0d0b15de6eaee6c3975e13ad2b0e1238d0fdd8f", "tree": "85161ae4639426e08b7804976f4e9910bde68dbb", "parents": [ "ad1244b2e7588df2f4e66747e1355016d6d014bc" ], "author": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Fri Sep 27 00:04:30 2013 -0700" }, "committer": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Fri Sep 27 00:04:30 2013 -0700" }, "message": "Upgrade to tzcode2013f plus Android modifications (from tzcode2013d plus Android modifications).\n\nlocaltime.c and strftime.c are still quite different from upstream because of\nour extensions, but the other files continue to be identical, and the two\nexceptions should be otherwise identical.\n\nFrom the tzcode2013e release notes:\n\n Changes affecting Godthab time stamps after 2037 if version mismatch\n\n Allow POSIX-like TZ strings where the transition time\u0027s hour can\n range from -167 through 167, instead of the POSIX-required 0\n through 24. E.g., TZ\u003d\u0027FJT-12FJST,M10.3.1/146,M1.3.4/75\u0027 for the\n new Fiji rules. This is a more-compact way to represent\n far-future time stamps for America/Godthab, America/Santiago,\n Antarctica/Palmer, Asia/Gaza, Asia/Hebron, Asia/Jerusalem,\n Pacific/Easter, and Pacific/Fiji. Other zones are unaffected by\n this change. (Derived from a suggestion by Arthur David Olson.)\n\n Allow POSIX-like TZ strings where daylight saving time is in\n effect all year. E.g., TZ\u003d\u0027WART4WARST,J1/0,J365/25\u0027 for Western\n Argentina Summer Time all year. This supports a more-compact way\n to represent the 2013d data for America/Argentina/San_Luis.\n Because of the change for San Luis noted above this change does not\n affect the current data. (Thanks to Andrew Main (Zefram) for\n suggestions that improved this change.)\n\n Where these two TZ changes take effect, there is a minor extension\n to the tz file format in that it allows new values for the\n embedded TZ-format string, and the tz file format version number\n has therefore been increased from 2 to 3 as a precaution.\n Version-2-based client code should continue to work as before for\n all time stamps before 2038. Existing version-2-based client code\n (tzcode, GNU/Linux, Solaris) has been tested on version-3-format\n files, and typically works in practice even for time stamps after\n 2037; the only known exception is America/Godthab.\n\n Changes affecting API\n\n Support for floating-point time_t has been removed.\n It was always dicey, and POSIX no longer requires it.\n (Thanks to Eric Blake for suggesting to the POSIX committee to\n remove it, and thanks to Alan Barrett, Clive D.W. Feather, Andy\n Heninger, Arthur David Olson, and Alois Treindl, for reporting\n bugs and elucidating some of the corners of the old floating-point\n implementation.)\n\n The signatures of \u0027offtime\u0027, \u0027timeoff\u0027, and \u0027gtime\u0027 have been\n changed back to the old practice of using \u0027long\u0027 to represent UT\n offsets. This had been inadvertently and mistakenly changed to\n \u0027int_fast32_t\u0027. (Thanks to Christos Zoulos.)\n\n The code avoids undefined behavior on integer overflow in some\n more places, including gmtime, localtime, mktime and zdump.\n\n Changes affecting code internals\n\n Minor changes pacify GCC 4.7.3 and GCC 4.8.1.\n\n Changes affecting documentation and commentary\n\n Documentation and commentary is more careful to distinguish UT in\n general from UTC in particular. (Thanks to Steve Allen.)\n\nFrom the tzcode2013f release notes:\n\n Changes affecting API\n\n The types of the global variables \u0027timezone\u0027 and \u0027altzone\u0027 (if present)\n have been changed back to \u0027long\u0027. This is required for \u0027timezone\u0027\n by POSIX, and for \u0027altzone\u0027 by common practice, e.g., Solaris 11.\n These variables were originally \u0027long\u0027 in the tz code, but were\n mistakenly changed to \u0027time_t\u0027 in 1987; nobody reported the\n incompatibility until now. The difference matters on x32, where\n \u0027long\u0027 is 32 bits and \u0027time_t\u0027 is 64. (Thanks to Elliott Hughes.)\n\nChange-Id: I14937c42a391ddb865e4d89f0783961bcc6baa21\n" }, { "commit": "ce4783ce76a4ef888466e02e4c6f3a0a3910bce8", "tree": "4bc51cd70edd4df6d6489d1ff8b4472f293f27b4", "parents": [ "3db1f359e9f218f5f73a7a9f4d80e4be362a526e" ], "author": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Fri Jul 12 17:31:11 2013 -0700" }, "committer": { "name": "Elliott Hughes", "email": "enh@google.com", "time": "Fri Jul 12 17:52:44 2013 -0700" }, "message": "Upgrade to tzcode2013d.\n\nWell, kinda... localtime.c still contains a bunch of Android-specific\nhacks, as does strftime.c. But the other files are now exactly the same\nas upstream.\n\nThis catches up with several years of bug fixes, and fixes most of the\ncompiler warnings that were in this code. (Just two remain.)\n\nBug: 1744909\nChange-Id: I2ddfecb6fd408c847397c17afb0fff859e27feef\n" }, { "commit": "edbe7fc97bab7ff0684053d1be564330689bf3ad", "tree": "271db0992a091d68f17f073ba9573c4698f97ce1", "parents": [ "78bf5fc677a2d25d50598b01781eafacdb5e6afe" ], "author": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Wed Mar 18 22:20:24 2009 -0700" }, "committer": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Wed Mar 18 22:20:24 2009 -0700" }, "message": "auto import //branches/master/...@140412\n" }, { "commit": "1dc9e472e19acfe6dc7f41e429236e7eef7ceda1", "tree": "3be0c520fae17689bbf5584e1136fb820caef26f", "parents": [ "1767f908af327fa388b1c66883760ad851267013" ], "author": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Mar 03 19:28:35 2009 -0800" }, "committer": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Mar 03 19:28:35 2009 -0800" }, "message": "auto import from //depot/cupcake/@135843\n" }, { "commit": "1767f908af327fa388b1c66883760ad851267013", "tree": "4b825dc642cb6eb9a060e54bf8d69288fbee4904", "parents": [ "a799b53f10e5a6fd51fef4436cfb7ec99836a516" ], "author": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Mar 03 18:28:13 2009 -0800" }, "committer": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Mar 03 18:28:13 2009 -0800" }, "message": "auto import from //depot/cupcake/@135843\n" }, { "commit": "a27d2baa0c1a2ec70f47ea9199b1dd6762c8a349", "tree": "defd1cc07d16ad2f3b21154114e092d11c94c5bb", "parents": [], "author": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Oct 21 07:00:00 2008 -0700" }, "committer": { "name": "The Android Open Source Project", "email": "initial-contribution@android.com", "time": "Tue Oct 21 07:00:00 2008 -0700" }, "message": "Initial Contribution\n" } ] }