From: Hamish D <dmishd@gmail.com>
To: Shadowfirebird <shadowfirebird@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] gpg-options.rb: how to set always_trust
Date: Mon, 24 Jan 2011 10:34:28 +0000 [thread overview]
Message-ID: <AANLkTimTV+qSRrVzMd=u7Z1egi2njbiHf2qqQDqOChqY@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]
Interesting ... it may well be a bug. As well as your hooks, could you let
me know:
* your gpg key type, including whether you have a separate sub key for
signing. If your key is on public keyservers then the key ID could also be
useful.
* whether you use the gpgkey option in .sup/config.yaml
I'll look into it in the next few days. I might even try constructing a gpg
test suite for sup ...
Hamish Downer
On 24 Jan 2011 09:15, "Shadowfirebird" <shadowfirebird@gmail.com> wrote:
[-- Attachment #1.2: Type: text/html, Size: 632 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-01-24 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 8:25 Sebastian Lipp
2011-01-23 12:17 ` Michael Stapelberg
[not found] ` <AANLkTimJZiRE31R5KJBdqZv5L17qhKeLjbO4fWM5LfD2@mail.gmail.com>
2011-01-23 22:09 ` Sebastian Lipp
2011-01-24 9:15 ` Shadowfirebird
[not found] ` <AANLkTimrPK4Bt7z+uN5AkShp3uJSw3OdbR2A-R0p4RoA@mail.gmail.com>
[not found] ` <AANLkTimB43mBbe-3EvRxZHCK_n9-Xy0mL1MHRGSO6MTf@mail.gmail.com>
2011-01-24 10:34 ` Hamish D [this message]
2011-01-25 14:32 ` Sebastian Lipp
2011-01-30 23:04 ` Hamish
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='AANLkTimTV+qSRrVzMd=u7Z1egi2njbiHf2qqQDqOChqY@mail.gmail.com' \
--to=dmishd@gmail.com \
--cc=shadowfirebird@gmail.com \
--cc=sup-talk@rubyforge.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