Gnus development mailing list
 help / color / mirror / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
Cc: ding@gnus.org
Subject: Re: [Patch] Documentation for pgg-gpg-use-agent
Date: Wed, 26 Apr 2006 18:17:22 +0200	[thread overview]
Message-ID: <m2lktsgvl9.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <v964kwmk3t.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 26 Apr 2006 17:28:54 +0200")

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Sun, Apr 23 2006, Sascha Wilde wrote:
>
>> I attached a small patch, adding short documentation for
>> pgg-gpg-use-agent.
> [...]

> Thanks.  Installed in v5-10 with some modifications:
>
> 2006-04-26  Reiner Steib  <Reiner.Steib@gmx.de>
>
> 	* pgg.texi (Caching passphrase): Fix markup and typos.  Simplify.
>
> | @defvar pgg-gpg-use-agent
> | When using GnuPG (gpg) as PGP scheme you can use @code{gpg-agent} for
> | caching@footnote{Actually @code{gpg-agent} does not cache passphrases
> | but privat keys.  On the other hand, from a users point of view this
> | technical difference isn't visible.}.  If non-@code{nil} try to use a
> | running @code{gpg-agent}.  It defaults to @code{nil}.
> | @end defvar
>
> Is the second sentence in the footnote necessary?

I was uncertain my self, but I thought it might be a good idea to tell
the average user, that there is no need for him to worry about the
difference.  :-)

cheers
sascha
-- 
Sascha Wilde  :  "The PROPER way to handle HTML postings is to cancel
the article, then hire a hitman to kill the poster, his wife and kids,
and fuck his dog and smash his computer into little bits. Anything
more is just extremism."  -- Paul Tomblin

  parent reply	other threads:[~2006-04-26 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-23 14:29 Sascha Wilde
2006-04-26 15:28 ` Reiner Steib
2006-04-26 15:38   ` Simon Josefsson
2006-04-26 16:17   ` Sascha Wilde [this message]
2006-04-26 16:34     ` Stuart D. Herring
2006-04-26 20:30       ` Reiner Steib

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2lktsgvl9.fsf@kenny.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=ding@gnus.org \
    /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.
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 NNTP newsgroup(s).