profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/eggert/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Paul Eggert eggert UCLA Los Angeles

eggert/tz 903

Time zone database and code

noloader/gnulib 1

Unoffical fork of GNU portability library used for CI testing. Do not fork.

eggert/dateutil 0

Useful extensions to the standard Python datetime features

ppetrosyan/LONI-WebST 0

Web Based Server Terminal

push eventeggert/tz

Paul Eggert

commit sha 0291a2da1593c7d7e6e3859ba73d46b80291e0d4

, → .

view details

push time in a day

push eventeggert/tz

Paul Eggert

commit sha 70676ba074e29316d03c510e5d076352b020712d

Revert May patch to zone.tab This reverts the part of May’s “Merge timezones that are alike since 1970” patch that affected the zone.tab file, to avoid compatibility issues for Android mentioned by Almaz Mingaleev in: https://mm.icann.org/pipermail/tz/2021-September/030387.html * Makefile (check_tables): Allow zone.tab TZ values to be taken from 'backward'. * checktab.awk: Do not report an error for links in 'backward' that do not have zone.tab entries. * zone.tab: Revert the remaining part of May’s “Merge timezones that are alike since 1970” patch to this file.

view details

push time in a day

push eventeggert/tz

Paul Eggert

commit sha 29583c461a9705118560e02e69bb64a0bf2fce0c

Samoa no longer observes DST (Thanks to Geoffrey D. Bennett.) * NEWS: Mention this. * australasia: Last DST transition was April.

view details

push time in a day

push eventeggert/tz

Paul Eggert

commit sha 74ae3bc0b1f3dd5c19f8c717fe0b9f0372bbeb2a

tzfile.5: s/only/& if/ (thanks to Andreas Schwab)

view details

push time in 3 days

push eventeggert/tz

Paul Eggert

commit sha ce8c77c02a8171a01b3c5b9281b694ae56bba7b2

Match RFC 8536bis-01 better * NEWS: Mention this. * tzfile.5: The draft RFC 8536bis-01 came out today; match its wording better.

view details

push time in 3 days

push eventeggert/tz

Paul Eggert

commit sha 2ae4e0a483318db1e8cffbe14e7dea2e2a470391

Improve leap second table truncation doc * NEWS: Mention possible successor to RFC 8536, and relaxation on TZif reader’s restriction on gaps between leaps. * tzfile.5: Improve wording on leap second expiration. Specify correction before truncated leap second table more accurately, given how localtime.c behaves; for example, the first leap second is considered to be positive if and only if its correction is positive. Say what to do after leap second table expires. Add TZ="XXX3EDT4,0/0,J365/23" example. Say that positive leap seconds not at end of localtime minute have not been a practical problem yet. * tzfile.5, zic.8: Use \- (current font minus) instead of \(mi (math font minus).

view details

push time in 5 days

push eventeggert/tz

Paul Eggert

commit sha df12babf4ed23bae657d178cc79dd8bbcc2a3e0a

Don't mistruncate TZif files at leap seconds Without this fix, zic mishandles the command ‘zic -L leapseconds -r @1706745601 etcetera’ when ‘leapseconds’ is generated from the test data file mentioned in: https://mm.icann.org/pipermail/tz/2021-September/030385.html The resulting, incorrect TZif file causes ‘TZ=Etc/GMT date -r 1706745601’ to output "Thu Feb 1 00:00:01 GMT 2024" instead of the correct "Thu Feb 1 00:00:00 GMT 2024", because localtime misinterprets the leap second entry at 1706745601 to be a positive instead of a negative leap second. * NEWS: Mention the fix. * zic.c (limitrange): When omitting leading leap seconds, do not output a leap second table that starts with a positive leap second with a nonpositive correction (or with a negative leap second with a positive correction) as that will confuse TZif readers into thinking the positive leap second is negative or vice versa. Instead, keep otherwise-unnecessary leading leap seconds to avoid the confusion.

view details

push time in 7 days

push eventeggert/tz

Paul Eggert

commit sha 59885b2fc5971061a8e9d8aa336563963badfa83

Document more background of rolling leap seconds * zic.8: It looks like rolling leaps were rarely used in broadcasts.

view details

push time in 8 days

push eventeggert/tz

Paul Eggert

commit sha 56da1f2aa7edb4e39c147c7ecf1788991ad67d85

Document background of rolling leap seconds * zic.8: Give background for rolling leap seconds, adapted from email by Arthur David Olson in: https://mm.icann.org/pipermail/tz/2021-September/030368.html

view details

push time in 8 days

push eventeggert/tz

Paul Eggert

commit sha 9fee4ab46ea48e1a2bf755b4c9937cbfda49a077

zic -r is incompatible with rolling leaps * NEWS, zic.8: Mention this. * zic.c (leapadd): Report an error if the user tries it.

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha 93132d18ed792eefe57c3b87397651fa2ff2e3f8

Simplify zic's handling of -r This is refactoring; it should not affect user-visible behavior. * zic.c (struct timerange): New member pretrans. (limitrange): New arg locut. Use it to set r.pretrans. All callers changed. (writezone): Initialize the new member, to avoid undefined behavior. Simplify by using the new member.

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha 4170b91a1cca52ecdd1ed54c372b1fe45f573502

Fix tzfile.5 miswording (thanks to Tim Parenti).

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha 88d6ecd175f6b03fc8a4617529f1e0943174f1a6

Improve wording about ambiguous leapsec fix Problem reported by Michael Deckers in: https://mm.icann.org/pipermail/tz/2021-September/030362.html * NEWS, tzfile.5: Improve wording re leap seconds not at the end of a localtime minute. Say this occurs only with "right" zones.

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha a868401041d6b7467118c7fd8d67f916ced00a27

Use https: for opengroup in zic.8

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha 584c0cafb52324b852fd3d1ba2b137bb784deba0

Port ‘check_time_t_alternatives’ to oddball hosts * Makefile (TIME_T_ALTERNATIVES): Use int_least64_t instead of int64_t, as int64_t is not required by the C standard. Similarly for int32_t, uint32_t, uint64_t.

view details

push time in 9 days

push eventeggert/tz

Paul Eggert

commit sha 83b95809017c60bff8dbccac6a0d713aaa166bb7

Fix ambiguous leapsecs by rolling up to a minute This fixes a longstanding ambiguity in the output of localtime in oddball timezones where a positive leap second occurs when the UTC offset is not a multiple of 60 seconds. See NEWS for details. * NEWS: Describe fix. * localtime.c (timesub): Use "??:??:60" at the end of the localtime minute containing the leap second, even when the second marked "??:??:60" is not itself a leap second. This avoids ambiguity in localtime output, at the cost of having the localtime leap second occur up to a minute away from the UTC leap second when the UTC offset is not a multiple of 60 seconds. * tzfile.5: Document the fixed and unfixed behaviors.

view details

push time in 10 days

push eventeggert/tz

Paul Eggert

commit sha 1103a98964dda86205ea48fa6ecb67cf29f32890

Omit some casts * localtime.c (getsecs, localsub, timesub): * strftime.c (_fmt): * zdump.c (dumptime): * zic.c (rcomp, atcomp): Rely on automatic conversions instead of casts, which are more error-prone.

view details

push time in 10 days

push eventeggert/tz

Paul Eggert

commit sha 96912bb31a83126fa727b5ff201b9efab45932ac

Fix tzfile.h comment * tzfile.h (struct tzhead): Update comment for version 4.

view details

push time in 10 days

push eventeggert/tz

Paul Eggert

commit sha f5a55467cf822e5375f725892d4db541dacd5a25

Change is_digit from macro to function This is cleaner and should be no slower with modern optimizers. * localtime.c, zdump.c (is_digit): New static function, replacing the old macro. * private.h (is_digit): Remove this macro.

view details

push time in 10 days

push eventeggert/tz

Paul Eggert

commit sha bb938549aba819f3ff881dc28f8aa848391e72f8

Relax leap-second pickiness * localtime.c (tzloadbody): Relax requirements on the leap second table in a TZif file, to accommodate truncation at the start that is less than 28 days before a leap second, or (unlikely, though theoretically possible) expiration less than 28 days after the last leap second.

view details

push time in 11 days

push eventeggert/tz

Paul Eggert

commit sha ffe80a11c222ac9e0e05caa666511fb1eeb6150e

White space fixes

view details

push time in 11 days

push eventeggert/tz

Paul Eggert

commit sha 9296ea527dbdf2b6027d31273bdee3e3c0128904

Mention time-tzdb and Timezone Database Explorer * tz-link.html: Mention these (thanks to Kerry Shetline).

view details

push time in 19 days

pull request commenteggert/tz

Change Europe/Kiev to Europe/Kyiv to use correct spelling

So, any updates on this topic?

Yes, Victor Perov sent email to the tz mailing list and it was replied to; see the followup thread there.

victor-perov

comment created time in a month

push eventeggert/.github

Paul Eggert

commit sha e50d717106c4f748b8463e4d13eab2f40eac209c

Create pull_request_template.md

view details

push time in a month

create barncheggert/.github

branch : main

created branch time in a month

created repositoryeggert/.github

created time in a month

PR closed eggert/tz

Resolve clang analyzer warning for localtime.c

If malloc() yielded NULL but also left or set errno to 0 (under very un-POSIX-y circumstances like private malloc implementations), then tzload would effectively signal success to its caller though there it was no success, and code branches would execute that were not meant to be executed.

clang said:

localtime.c:321:16: warning: The right operand of '<' is a garbage value [core.UndefinedBinaryOperatorResult] for (i = 0; i < sp->charcnt; ++i)

+12 -8

1 comment

1 changed file

jengelh

pr closed time in a month

pull request commenteggert/tz

Resolve clang analyzer warning for localtime.c

I replied on the tz mailing list.

jengelh

comment created time in a month

push eventeggert/tz

Paul Eggert

commit sha 5c79ca1f7b574798dc5f05ab0eeaae30ceb948e4

* Makefile: Document HAVE_MALLOC_ERRNO.

view details

push time in a month

push eventeggert/tz

Paul Eggert

commit sha d9b364304b9f56e7c94252e84829efba3804417b

Port to platforms where malloc does not set errno Problem reported via clang by Jan Engelhardt in: https://mm.icann.org/pipermail/tz/2021-August/030319.html * date.c (dogmt): * localtime.c (tzload, tzalloc) [!HAVE_MALLOC_ERRNO]: * zdump.c (xmalloc): * zic.c (memcheck): Don’t assume failing malloc sets errno. * private.h (HAVE_MALLOC_ERRNO): Default to 1. (EINVAL): Default to ERANGE since even C89 requires ERANGE. This is probably just theoretical. (ENOMEM): Default to EINVAL.

view details

push time in a month