summaryrefslogtreecommitdiff
path: root/win32/README.TZ
diff options
context:
space:
mode:
authorKim Kibum <kb0929.kim@samsung.com>2012-08-24 14:34:26 +0900
committerKim Kibum <kb0929.kim@samsung.com>2012-08-24 14:34:26 +0900
commit4acc22dd2f30f063c7b07fdbc911384feeda58eb (patch)
treea78b9ba604297cddb9a23424ccc8abfc6ae7ba94 /win32/README.TZ
parent3101b2a7be8f0e3cc6ff469ce2597945c862264b (diff)
downloadzip-4acc22dd2f30f063c7b07fdbc911384feeda58eb.tar.gz
zip-4acc22dd2f30f063c7b07fdbc911384feeda58eb.tar.bz2
zip-4acc22dd2f30f063c7b07fdbc911384feeda58eb.zip
upload source
Diffstat (limited to 'win32/README.TZ')
-rw-r--r--win32/README.TZ7
1 files changed, 7 insertions, 0 deletions
diff --git a/win32/README.TZ b/win32/README.TZ
new file mode 100644
index 0000000..ddce3f8
--- /dev/null
+++ b/win32/README.TZ
@@ -0,0 +1,7 @@
+From: paul.kienitz@shelter.sf.ca.us (Paul Kienitz)
+> It looks like I don't have to create a tzset() kluge for Watcom to check
+> the win32 API timezone information after all -- their new 10.6 release has
+> corrected this oversight. The TZ variable overrides the API. So the only
+> win32-related patch I want to make for Zip is just to use USE_EF_UT_TIME
+> unconditionally. With this in place, timezone stuff is working flawlessly
+> with or without TZ being set.