From: Rich Lane <rlane@club.cc.cmu.edu>
To: Hamish D <dmishd@gmail.com>
Cc: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Converted crypto to use the gpgme gem
Date: Thu, 23 Dec 2010 13:43:45 -0500 [thread overview]
Message-ID: <1293129774-sup-3146@zyrg.net> (raw)
In-Reply-To: <AANLkTi=AJZGLAra20fQvEvU0EasQ_1yWpsr6+4TV3iEn@mail.gmail.com>
All 5 patches applied to branch gpgme and merged to next.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-12-23 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:08 Hamish D
2010-11-08 11:21 ` Hamish D
2010-11-08 22:32 ` Hamish D
2010-11-11 9:09 ` Gaudenz Steinlin
2010-11-11 17:25 ` Hamish D
2010-11-16 11:42 ` Gaudenz Steinlin
2010-11-16 14:20 ` Hamish D
2010-11-16 18:36 ` Gaudenz Steinlin
2010-11-16 23:05 ` Hamish D
2010-11-28 22:51 ` Hamish D
2010-11-29 9:41 ` Gaudenz Steinlin
2010-11-30 6:22 ` Tero Tilus
2010-12-01 8:37 ` Gaudenz Steinlin
2010-12-06 23:31 ` Hamish D
2010-12-23 18:43 ` Rich Lane [this message]
2011-01-19 3:11 ` Rich Lane
2011-01-30 23:57 ` Hamish D
2011-01-30 23:59 ` Hamish D
2011-01-19 16:12 ` Alvaro Herrera
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=1293129774-sup-3146@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=dmishd@gmail.com \
--cc=sup-devel@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