message.texi: Remove reference to gpg-2comp

Signed-off-by: Julien Danjou <julien@danjou.info>

diff --git a/texi/ChangeLog b/texi/ChangeLog
index dfd2531..c76b1c1 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,5 +1,8 @@
 2010-10-06  Julien Danjou  <julien@danjou.info>
 
+       * message.texi (PGP Compatibility): Remove reference to gpg-2comp,
+       broken link.
+
        * Makefile.in: Remove xml2texi stuff.
 
        * gnus-faq.texi (FAQ 8-3): Remove references to my.gnus.org.

diff --git a/texi/message.texi b/texi/message.texi
index cf52274..68341ba 100644 (file)
--- a/texi/message.texi
+++ b/texi/message.texi
@@ -1149,11 +1149,8 @@ If you have imported your old PGP 2.x key into GnuPG, and want to send
 signed and encrypted messages to your fellow PGP 2.x users, you'll
 discover that the receiver cannot understand what you send. One
 solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
-@code{pgg-default-scheme} to @code{pgp}).  If you do want to use
-GnuPG, you can use a compatibility script called @code{gpg-2comp}
-available from
-@uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}.  You
-could also convince your fellow PGP 2.x users to convert to GnuPG.
+@code{pgg-default-scheme} to @code{pgp}). You could also convince your
+fellow PGP 2.x users to convert to GnuPG.
 @vindex mml-signencrypt-style-alist
 As a final workaround, you can make the sign and encryption work in
 two steps; separately sign, then encrypt a message.  If you would like