From: Chong Yidong <cyd@stupidchicken.com>
Cc: wilde@sha-bang.de, emacs-devel@gnu.org
Subject: Re: Documenting gpg-agent
Date: Sun, 24 Dec 2006 15:55:41 -0500 [thread overview]
Message-ID: <87k60hm2sy.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1GyWrH-0002Zd-1V@fencepost.gnu.org> (Richard Stallman's message of "Sun\, 24 Dec 2006 12\:09\:59 -0500")
Richard Stallman <rms@gnu.org> writes:
> > 1. It should have an Info xref to the proper node in the other manual.
> > "Please refer to the documentation of GnuPG" is not sufficient.
> >
> > 2. Just an xref is not enough. This needs to actually explain the
> > simple usage of gpg-agent.
> >
> > 3. If this is the preferred method, to avoid a security hole,
> > then we should remove or deprecate other methods.
>
> How aboout this?
>
> *** emacs/man/pgg.texi.~1.14.~ 2006-12-17 18:16:25.000000000 -0500
> --- emacs/man/pgg.texi 2006-12-23 20:04:50.000000000 -0500
> ***************
>
> Your change takes care of #1 and #3, but doesn't do #2.
> Please install the change, but we need a little more.
Done.
next prev parent reply other threads:[~2006-12-24 20:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 14:59 Documenting gpg-agent Richard Stallman
2006-12-17 18:44 ` Sascha Wilde
2006-12-17 18:56 ` Sascha Wilde
2006-12-18 15:59 ` Richard Stallman
2006-12-23 17:04 ` Ken Manheimer
2006-12-23 17:25 ` David Kastrup
2006-12-23 18:11 ` Ken Manheimer
2006-12-24 1:35 ` Richard Stallman
2006-12-24 22:45 ` Daiki Ueno
2006-12-25 16:53 ` Richard Stallman
2006-12-26 1:01 ` Daiki Ueno
2006-12-28 14:21 ` Sascha Wilde
2007-02-15 16:33 ` Ken Manheimer
2007-02-17 20:57 ` Richard Stallman
2006-12-25 17:39 ` Ken Manheimer
2006-12-17 23:19 ` Chong Yidong
2006-12-18 15:59 ` Richard Stallman
2006-12-24 1:06 ` Chong Yidong
2006-12-24 17:09 ` Richard Stallman
2006-12-24 20:55 ` Chong Yidong [this message]
2006-12-25 17:37 ` Chong Yidong
2006-12-26 17:22 ` Richard Stallman
2006-12-31 13:08 ` Sascha Wilde
2006-12-31 22:13 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k60hm2sy.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=wilde@sha-bang.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).