X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=ChangeLog;h=b03b6e6bc7ea03df72faff982d7af6c4a0a743cb;hp=26045ed1f5299c994191245ccba7aab2a1d208b6;hb=e7f0dbf0856b7eb1f97f4c95fe39497b1ca97998;hpb=2c0f411d65a869c6020fa1b624aa56acaa8636ff diff --git a/ChangeLog b/ChangeLog index 26045ed..b03b6e6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,61 @@ +Tue Mar 28 16:17:39 2000 Doug Morris + + * applied Todd Miller's patch to + dropsbr.c to prevent core dumping on packf. Here's the note + from his message: + + Since sizeof(buffer) == sizeof(tmpbuffer) packf will dump + core on a file w/o a From line with a line >= BUFSIZ. + I noticed this because I had a junk file in my mail + spool somehow. + +Fri Mar 17 11:59:33 2000 Dan Harkless + + * wesley.craig@umich.edu did not document his previous KPOP patch, + so I did so, and asked him to check what I wrote. Unfortunately + he didn't notice my misunderstanding of his patch. I wrote that + if you #define POPSERVICE "kpop", inc and msgchk will use KPOP + exclusively, but if you leave it as "pop3", you can use Wesley's + new -kpop switch on a given invocation. Instead, however, -kpop + turned out to be necessary on every invocation, and a KPOP user + complained. Applied Wesley's new patch, which makes things work + like I thought his original patch did. After that, did one more + clarifying pass to the documentation in inc.man and msgchk.man. + +Wed Mar 15 18:45:45 2000 Dan Harkless + + * When I fixed the long-standing makedir() bugs in January, I had + the code call strtoul(..., 0), which I believed to be safe as all + modes specified as ASCII constants in the nmh code started with a + leading zero (signifying octal), which I did as it would work if + internal constants were ever changed to hex. Unfortunately I was + unaware of the "Folder-Protect:" .mh_profile entry, which + mh-profile.man documents as an octal-only constant, with no + leading zero required. I've changed the strtoul() call to an + atooi() call and removed the misleading leading zeroes on the + ASCII octal constants in the code and man pages. Also changed the + "Folder-Protect:" example in the man page to something more + interesting than a duplication of the default. + + * When I added my --enable-masquerade option, you'll note that I + didn't make it --enable-nmh-masquerade. I find the --enable-nmh-* + options too wordy and I'm not sure why Richard went that route. + I've renamed them to just --enable-*, but the old versions will + still work as well (they just aren't advertised). + + * Added a line to the "nmh configuration" output saying whether + POP is enabled. + + * Added a new README.developers file. From the file: + + This file is intended to provide a few tips for anyone doing + development on nmh. Developers who learn things "the hard + way" about the nmh codebase (as opposed to local info best + encoded in a comment) are encouraged to share their wisdom + here. + + Currently the topics are "autoconf files" and "directory structure". + Tue Mar 14 12:41:48 2000 Dan Harkless * Applied, after some finessing, @@ -215,11 +273,12 @@ Fri Jan 28 17:39:24 2000 Dan Harkless Thu Jan 27 12:22:25 2000 Dan Harkless - * makedir() had multiple bugs dating back to MH. It passed an - octal constant to atoi(), which interpreted it as decimal, - resulting in directories with no user read or execute permissions, - making nested directory creation fail. Also, when creating a - nested directory, correct permissions were only set on the inner one. + * makedir() had multiple bugs dating back to MH. An octal + constant was apparently being interpreted as decimal, resulting in + directories with no user read or execute permissions, making + nested directory creation fail. And there wasn't even an + _attempt_ to set desired permissions (e.g. from "Folder-Protect:" + in .mh_profile) on the outer directories of a nested directory. * A second `make install' would always fail because the check for whether mh_profile.5 existed was written incorrectly.