20 Nov
2017
20 Nov
'17
11:11 p.m.
Tom Lane wrote:
would it be reasonable to request that that file contain some version-identifying info?
Although we've avoided putting a version number into the existing binary format due to compatibility concerns, adding a comment to tzdata.zi shouldn't be so constrained. How about the attached patch? It prepends the following comment line to tzdata.zi in the current development version: # version 2017c-18-ga5a40b4 Here, "2017c-18-ga5a40b4" has the same meaning as in the file 'version': release 2017c plus 18 updates, with a Git checksum of a5a40b4. If the working files have uncommitted changes, the version string has "-dirty" appended.