[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded vm 6.93-1 (sparc) to ftp-master



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed,  4 Jul 2001 14:31:49 -0500
Source: vm
Binary: mime-codecs vm
Architecture: sparc
Version: 6.93-1
Distribution: unstable
Urgency: low
Maintainer: Debian GNU/Linux SPARC/UltraSPARC Build Daemon <buildd@sparc.debian.org>
Changed-By: Manoj Srivastava <srivasta@debian.org>
Description: 
 mime-codecs - Fast Quoted-Printable and BASE64 MIME transport codecs
Changes: 
 vm (6.93-1) unstable; urgency=low
 .
   * New upstream version.
   * Excerpted changes:
       * New variables:
         + vm-folder-file-precious-flag
       * added CRAM-MD5 as an authentication method for IMAP.
       * vm-su-do-date: interpret 2-digit years in the RFC-822 matching
         case as 20XX if year starts with 0-6.
       * vm-rfc1153-or-rfc934-burst-message: skip spaces in addition to
         newlines that occur after a separator line.  A digest has been
         observed with that kind of deformity.
       * treat enable-local-eval as we do enable-local-variables--- always
         bind it to nil.
       * vm: don't bind vm-auto-decode-mime-messages non-nil during
         initial message preview if it is nil.
       * vm-mime-display-internal-text/html: dropped (sleep-for 2).  No one
         cares enough about the "Need W3 to inline HTML" message to wait 2
         seconds afterward.
       * added menu entry to allow MIME objects to be converted to
         another type and displayed.  The new type is determined by
         vm-mime-type-converter-alist.
       * added koi8-r to vm-mime-mule-charset-to-coding-alist (XEmacs only).
       * vm-pop-read-list-response: check for nil return of
         vm-pop-read-response before using return value.
       * vm-pop-read-stat-response: check for nil return of
         vm-pop-read-response before using return value.
       * vm-encode-coding-region: use unwind-protect to make sure (well
         more likely) that the work buffer always gets killed if it has
         been created.
       * vm-decode-coding-region: use unwind-protect to make sure (well
         more likely) that the work buffer always gets killed if it has
         been created.
       * vm-mime-convert-undisplayable-layout: put object buffer on
         garbage list sooner to make rarer the situation where the
         buffer never gets deleted.
       * Makefile: remove function definition of vm-its-such-a-cruel-world
         after it is run.
       * vm-md5-region: if vm-pop-md5-program exits non-zero, signal an
         error.  Also if the work buffer is not at least 32 bytes long,
         signal an error.  This prevents naive callers from assumption all
         is well and using a possibly empty string as an MD5 hash.
       * vm-md5-region: check the MD5 digest returned for non-hex-digit
         characters and signal an error if any are found.
       * vm-get-file-buffer: use find-buffer-visiting if it is fbound.
       * vm-build-threads: fixed loop that removed child messages from a
         parent when better information about a child's parent is found.
         Previously the loop attempted to remove the same message from
         the parent over and over.
       * vm-build-threads: gather thread data using References and
         In-Reply-To for all messages before using the Subject header.
         This helps prevent the case where References says A is the
         parent of B but because of clock skew B is older than A, which
         can lead to B being considered the parent of A if A and B have
         the same subject and vm-thread-using-subject is non-nil.
Files: 
 322ac34051df7afbe26d6a32c28b0d05 50772 utils optional mime-codecs_6.93-1_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>

iEYEARECAAYFAjtE3cYACgkQgD/uEicUG7BeMgCfQTxyNfEcAP1/E+8gRpfVjpOt
jNMAoMPzocluz0a//jawp+NLZJbE1b3o
=4YLH
-----END PGP SIGNATURE-----



Reply to: