emacs-19.31-1 uploaded
Ian Murdock said "by all means..." put this together. I've tweaked the
rules and control files a bit to make things even more automated (in
theory, it should work on 19.32 without *any* changes - in practice,
we'll see :-)
I'm going over the bug reports too. I think the @-sign bug is gone,
now, though...
[These are signed with the <eichin@cygnus.com> key. I should have a
eichin@kitten.gen.ma.us key soon, but I'm experimenting with a few
things first, hope nobody minds. eichin@cygnus.com is at least on the
keyservers already...]
-----BEGIN PGP SIGNED MESSAGE-----
Date: 30 May 96 04:36 UT
Format: 1.5
Distribution: unstable
Priority: Low
Maintainer: Mark Eichin <eichin@kitten.gen.ma.us>
Source: emacs
Version: 19.31-1
Binary: emacs
Architecture: i386 source
Description:
emacs: The GNU Emacs editor.
Changes: upgrade to 19.31.
Files:
e69bd76c4d5c2200fc8e27a6d18ff29f 10376515 - emacs-19.31-1.tar.gz
323220769c3dc2c796e9cfdec6a0efac 3609 - emacs-19.31-1.diff.gz
5a05f01206b194562e2da9bb082f0e52 4794738 misc extra emacs-19.31-1.i386.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMa0oXly/7Dlmzom3AQGahwP+Jtx2sLzy5svfb3CsYBd1Gw1wDd4AMTRg
HCKAGepGdwltGUz6BGQfDVxAtMsVCXUZJQp3Ch99/m5l6ItffSkvJMfwqnKC3u6L
C0l2Rz8Ok3vRo/nc1tnK+dhgtgV4V5l7+yqauuNxZm3JOXic4xaGeSo/wEFTr7cT
PaV7PE9AfQw=
=cT4o
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Date: 30 May 96 04:36 UT
Format: 1.5
Distribution: unstable
Priority: Low
Maintainer: Mark Eichin <eichin@kitten.gen.ma.us>
Source: emacs-el
Version: 19.31-1
Binary: emacs-el
Architecture: all
Description:
emacs-el: GNU Emacs LISP (.el) files.
Changes: upgrade to 19.31
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMa0ocly/7Dlmzom3AQG4qwP9HQ5lyc0Cq6+Vww4Qc+VvOpUlz48JMAzF
Ls+8ggB8WCXpqb2NfO3qsN1BgMT70uAPbWcyXf7GY0OSI9sPifunl1w2sFfWDviA
M79yYB9hJifY7rRqnNQwGuaEtm3Xyfpo9HN1iy+llI/jx4M5iScgKyLmNlJOiv5e
aYJH+WK8Ukc=
=tHQ1
-----END PGP SIGNATURE-----
Reply to: