From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Getting gpg to work
Date: Wed, 27 May 2009 09:25:44 -0700 [thread overview]
Message-ID: <1243441483-sup-2270@entry> (raw)
In-Reply-To: <87k5462s8q.fsf@pond.riseup.net>
Reformatted excerpts from Micah Anderson's message of 2009-05-24:
> I'm getting gpg messages that aren't being decoded automatically.
In the early part of Sup's log, does it mention being able to find the
gpg binary? (When in Sup, hit b until you see the log-mode buffer and
then scroll to the top.)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-27 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 19:52 Micah Anderson
2009-05-27 16:25 ` William Morgan [this message]
2009-05-29 4:19 ` Micah Anderson
2009-05-31 0:48 ` William Morgan
2009-11-10 23:47 ` Micah Anderson
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=1243441483-sup-2270@entry \
--to=wmorgan-sup@masanjin.net \
/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