From: Hamish <dmishd@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sending Encrypted and Signed emails with gpg
Date: Sun, 01 May 2011 19:51:20 +0100 [thread overview]
Message-ID: <1304272466-sup-6692@whisper> (raw)
In-Reply-To: <1304115809-sup-4326@localhost>
Excerpts from Paul Grove's message of Fri Apr 29 23:29:42 +0100 2011:
> Hi, I'm using git://gitorious.org/sup/mainline.git and am uptodate as of
> 29/04/2011
Are you using the master branch? Or next? I've done a lot of work on
sup's gpg support recently. The next branch uses the gpgme library
rather than the gpg binary. If you're using master, then try switching
to next (git checkout next) and see if that fixes your issues.
> I'm not entirely sure how long it has been like this for me, but I know
> it used to work. I use a mailing list that only accepts encrypted and
> signed emails which used to work fine but it is currently rejecting my
> emails.
I also use a list like that, and sup works fine for me, so I'd like it
to work for you aswell.
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-05-01 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:29 Paul Grove
2011-05-01 18:51 ` Hamish [this message]
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=1304272466-sup-6692@whisper \
--to=dmishd@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