From: ueno <ueno>
Date: Wed, 12 Apr 2006 09:45:34 +0000 (+0000)
Subject: PGG -> Gnus/PGG
X-Git-Tag: epgsm-branchpoint~103
X-Git-Url: http://git.chise.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=478e44b89438bc4e2d219e1782fc48c829a36d12;p=elisp%2Fepg.git

PGG -> Gnus/PGG
---

diff --git a/README b/README
index 0367448..95b786b 100644
--- a/README
+++ b/README
@@ -34,16 +34,16 @@ add the following line to your ~/.gnus.
 
 * Advantages over other competitors
 
-There are many competitors of EasyPG such as Mailcrypt, PGG, gpg.el,
-etc.  EasyPG has some advantages over them.
+There are many competitors of EasyPG such as Mailcrypt, Gnus/PGG,
+gpg.el, etc.  EasyPG has some advantages over them.
 
 ** EasyPG avoides potential security flaws of Emacs.
 
 *** `call-process-region' writes data in region to temporary files.
 
-`call-process-region' writes data in region to temporary files.  PGG
-and gpg.el use `call-process-region' to communicate with a gpg
-subprocess.  Your passphrases leak to the filesystem!
+`call-process-region' writes data in region to temporary files.
+Gnus/PGG and gpg.el use `call-process-region' to communicate with a
+gpg subprocess.  Your passphrases leak to the filesystem!
 
 *** There is no way to clear strings safely.
 
@@ -53,8 +53,8 @@ strings by `(fillarray string 0)'.  However, Emacs performs compaction
 in gc_sweep phase.  If GC happens before `fillarray', passphrase
 strings may be moved elsewhere in memory.  It is recommended that as
 soon as you are done with passphrase you should clear it manually.
-However, PGG and gpg.el can keep passphrase strings in cache for a
-while and this behavior is their default!
+However, Gnus/PGG and gpg.el can keep passphrase strings in cache for
+a while and this behavior is their default!
 
 ** GnuPG features are directly accessible from Emacs