+Fri Apr 14 17:59:43 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Upped the version number to 1.0.4+dev.
+
+Fri Apr 14 17:50:36 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Added new files README.developers, ChangeLog_MH-3_to_MH-6.6, and
+ ChangeLog_MH-6.7.0_to_MH-6.8.4.html to DIST target in Makefile.in.
+
+ * Released nmh-1.0.4.
+
+Fri Apr 14 17:50:36 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Added new files README.developers, ChangeLog_MH-3_to_MH-6.6, and
+ ChangeLog_MH-6.7.0_to_MH-6.8.4.html to DIST target in Makefile.in.
+
+ * Released nmh-1.0.4.
+
+Tue Apr 11 21:37:03 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Applied Brian Campbell <bacam@tardis.ed.ac.uk>'s mhn.defaults.sh
+ patch:
+
+ It appears that there shouldn't be quotes around the %s in the
+ iso-8859-1 charset entry; xterm passes the remaining arguments
+ to the program, quoting them means that xterm thinks they're
+ part of the program's name.
+
+ This %s isn't the same as the "Insert content subtype" one from
+ mhshow-show-* -- it doesn't come from MIME headers and is safe not
+ to quote.
+
+Sun Apr 09 13:03:59 2000 Doug Morris <doug@mhost.com>
+
+ * added check in fmt_compile() to handle a single-character
+ format string. fmt_compile() depends on having an array of
+ format characters with an empty item at the end. A
+ single-character format would cause programs using this
+ function to segfault because the algorithm used to decide on
+ the length of the array mistakenly created a single-item array
+ when the format string was one character. This eventually
+ caused problems when the program attempted to test item+1
+ in the array.
+
+Thu Apr 06 21:53:50 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Richard Coleman threw out a lot of old MH-specific files in nmh.
+ Much of the stuff, indeed, is not worth saving, but there are
+ nuggets that are very worthwhile, and should probably be added
+ back in. Most important, IMHO, are the MH change logs, as they
+ can help answer questions like "Why is this code like this?" or
+ "How long has this been broken?" or "What was this ever used for?"
+
+ I've added a new file to the nmh tree called
+ ChangeLog_MH-3_to_MH-6.6. It's cobbled together from the
+ mh-6.8.4/papers/mh*/MHCHANGES files. I've re-ordered the entries
+ to go from newest at the top to oldest at the bottom to match the
+ ChangeLog convention. Unfortunately there are no change logs for
+ versions of MH prior to 3 in the MH tar files available at
+ <ftp://ftp.ics.uci.edu/pub/mh>. Also, it appears to me that there
+ are MH-6.6 changes that aren't documented in the logs.
+
+ I've also added ChangeLog_MH-6.7.0_to_MH-6.8.4.html. This is
+ based on mh-6.8.4/papers/changes/mh-changes.ms. The nroff format
+ and its "catman"-type output are a pain to deal with, but I was
+ loath to throw away the formatting, so I converted the file to
+ HTML. The only actual markup in the body are the "<B>" and "<U>"
+ tags, and "<" and ">" instead of '<' and '>', so it's quite
+ doable to view the file in plain ASCII mode as well. Note that
+ some of the changes this file documents as having been made in
+ MH-6.8.4 may not be present in nmh -- Richard started with 6.8.3
+ and later put in certain 6.8.4 stuff.
+
+Wed Apr 05 21:09:28 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+ * Applied Eric Schnoebelen <eric@cirr.com>'s mhshowsbr.c patch
+ fixing apparent bugs in Dan Winship's new security quoting code:
+
+ Since upgrading, I've been getting the following errors
+ while attempting to process some MIME messages:
+
+ (1) Syntax error: Unterminated quoted string
+ exit 2
+
+ and:
+
+ (2) line 1/10 (END)Segmentation fault (core dumped)
+
+ (2) appears to be due to the testing of an unset pointer in
+ mhshowsbr.c:show_multi_aux(). (1) appears to be caused by
+ mis-quoting a filename being handed to the shell in
+ mhshowsbr.c:show_content_aux().
+
+ Resolving the pointer reference issue in
+ mhshowsbr.c:show_multi_aux() turned up a similar mis-quoting
+ problem in the routine.
+
+Tue Mar 28 16:17:39 2000 Doug Morris <doug@mhost.com>
+
+ * Applied Todd.Miller@courtesan.com'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 <dan-nmh@dilvish.speed.net>
+
+ * 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 <dan-nmh@dilvish.speed.net>
+
+ * 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".
+
projects / mmh / blobdiff