X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=ChangeLog;h=2b03f0adb4d16f400c4fa526936a0a524a3624b7;hp=a5e306c5a421e86fd7d950348f0b3b261c08639e;hb=de84e33cbf49bf0e70ad010d58ab9893c5438cff;hpb=673b2a0af17a1dd96c21ae9712accee5324f24cf

diff --git a/ChangeLog b/ChangeLog
index a5e306c..2b03f0a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,48 @@
+Wed May 31 07:40:45 2000 Doug Morris <doug@mhost.com>
+
+	* added a lint target to the Makefiles and a check in autoconf
+	to determine whether lint or lclint exists on the system. 
+
+Fri May 30 19:21:48 2000 Dan Harkless <dan-nmh@dilvish.speed.net>
+
+	* etc/Makefile.in was incorrectly installing mts.conf.in and
+ 	sendfiles.in -- fixed.  Generated sendfiles script was not a
+ 	dependency of the `all' target, and was incorrectly included in
+ 	the distribution.  Changed the suffix for the backed-up previous
+ 	versions of the etc files from the ambiguous .old to .prev.  Added
+ 	call to diff -- only keep the .prev files around if different from
+ 	the newly-installed versions (intentionally didn't redirect output
+ 	to /dev/null so you'll notice when your changed versions are
+ 	getting moved aside).
+
+	* INSTALL never documented the etc/*.old thing.  Documented the
+	new etc/*.prev thing (including a note to watch for diff output).
+
+	* Applied Alec Wolman <wolman@cs.washington.edu>'s dropsbr.c patch:
+
+	    In the map_write routine, a call is made to map_open and this
+ 	    call is supposed to set the "clear" variable to 0 or 1,
+ 	    depending on whether the map file is empty or not.  In
+ 	    mh6.8.3, this worked because map_open would set "clear" by
+ 	    calling the mbx_Xopen routine.  In nmh, the code for mbx_Xopen
+ 	    was merged into mbx_open, but the interface for mbx_open
+ 	    doesn't support the clear variable, so that functionality was
+ 	    lost.  The map_open interface still contains "int *clear" in
+ 	    the prototype, but never sets it.
+
+	    My patch eliminates "clear" from the map_open interface (I
+ 	    checked to make sure that map_write is the only client of
+ 	    map_open).  Furthermore, my patch also sets the "clear"
+ 	    variable properly at the beginning of map_write by calling
+ 	    fstat().  This eliminates the bug in that the value of "clear"
+ 	    being used later in the routine was just stack garbage.
+
+	    Having a bad value of clear causes this next bug to be
+ 	    triggered: The fp file pointer was being opened with fdopen,
+ 	    but in two of the three switch cases it wasn't being closed.
+  	    In certain cases, this was causing packf to run out of file
+ 	    descriptors if you attempted to pack a large folder.
+
 Mon May 29 7:48:15 2000 Shantonu Sen <ssen@mit.edu>
 
 	* Moved the date parsing routines from zotnet/tws to sbr/ (and