X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=ChangeLog;h=824f2a79372bab7c4be559d64ea7a4df49385a63;hb=97e7d6f2f5db4e8f09cb015ee6c2da2ff129f963;hp=f475a0129c2be57ffa63d405d24edfd54f2856dc;hpb=7394d9e002c22cb0ac9722fe51b877a7462efb3c;p=mmh diff --git a/ChangeLog b/ChangeLog index f475a01..824f2a7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,12 +1,28 @@ +Wed Sep 6 22:40:03 2000 Shantonu Sen + + * Tracked down the problem in the new dtimep where time + zones were being radically misreported. It was because the + parser knew about military time zones (such as M or E) but in + some cases did not know about the textual representation of + some zones (like MET). When it encountered one of these, the + date parser misread MET as the military time zone T (well, first + zone M, then E, and finally T). I took military zones out, and + things seem much better. Also, the default behavior of parsing + time zones appears to default to GMT in the absence of better + info, which is less bogus than assuming the mail came from the + current time zone, which was the behavior in 1.04. + Thu Aug 10 13:22:13 2000 Dan Harkless * Decided that limiting the message number columns to 3 on my scan.MMDDYY and scan.YYYYMMDD (to try to regain space taken by extra date info) was ill-conceived. It's not that tough to get past 999 messages, though I imagine it's rather rare to exceed - 9999. Changed these to 4. I had already removed the "replied / - encrypted" column in YYYYMMDD, but this time I removed it on - MMDDYY as well (I've never seen it used...). + 9999. Changed these to 4. Also put the "replied / encrypted" + column back in YYYYMMDD -- I've never seen it show anything but a + space, but that space is useful if you use scan, grep, and awk + (with the default field separator) to grab message numbers (I know + -- pick should really be used for these purposes...). Mon Aug 7 20:11:09 CEST 2000 Ruud de Rooij @@ -21,8 +37,10 @@ Thu Aug 03 17:14:08 2000 Dan Harkless Tue Aug 1 10:48:05 EDT 2000 Kimmo Suominen - * Fixed install in etc/Makefile.in so it wouldn't fail when - configuring and building outside the source tree. + * Makefile install rules should not look for generated files in + the source tree -- this will happen to work when configuring and + building inside the source tree but will fail when using an + external build tree. Fixed etc/Makefile.in. Mon Jul 24 16:20:45 2000 Dan Harkless