summaryrefslogtreecommitdiff
path: root/Y2KINFO
diff options
context:
space:
mode:
authorGlenn Randers-Pehrson <glennrp at users.sourceforge.net>2017-08-24 15:00:11 -0500
committerGlenn Randers-Pehrson <glennrp at users.sourceforge.net>2017-08-28 12:24:45 -0500
commitcc3d228369aa991458c28b5cd3e6b0e3f25764b8 (patch)
tree292fdc9d5437752a96ebfb26f51708af14ba5737 /Y2KINFO
parent47c8646c9c4b6a5d422f226a822e098e2e7ae56a (diff)
downloadlibpng-cc3d228369aa991458c28b5cd3e6b0e3f25764b8.tar.gz
[libpng10] Imported from libpng-1.0.68.tarv1.0.68libpng10
Diffstat (limited to 'Y2KINFO')
-rw-r--r--Y2KINFO4
1 files changed, 2 insertions, 2 deletions
diff --git a/Y2KINFO b/Y2KINFO
index 005525fa6..aae91c502 100644
--- a/Y2KINFO
+++ b/Y2KINFO
@@ -1,13 +1,13 @@
Y2K compliance in libpng:
=========================
- December 29, 2016
+ August 24, 2017
Since the PNG Development group is an ad-hoc body, we can't make
an official declaration.
This is your unofficial assurance that libpng from version 0.71 and
- upward through 1.0.67 are Y2K compliant. It is my belief that earlier
+ upward through 1.0.68 are Y2K compliant. It is my belief that earlier
versions were also Y2K compliant.
Libpng only has three year fields. One is a 2-byte unsigned integer