From: "ken manheimer" <ken.manheimer@gmail.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: Leo <sdl.web@gmail.com>, emacs-devel@gnu.org
Subject: Re: Should pgg be mark obsolete?
Date: Mon, 22 Dec 2008 13:22:21 -0500 [thread overview]
Message-ID: <2cd46e7f0812221022k95ad016k115f3bc47a22cebf@mail.gmail.com> (raw)
In-Reply-To: <jwvocz56i5t.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
first, thanks for looking out for allout. i need to investigate the switch
to epg, hope i'll have the time soon. time is a challenge, plus i do some
tricky things with the pgg password cache that i would need to duplicate in
the transition, and am nervous that will increase the challenge
significantly. i'm not sure anyone can advise me without investigating the
allout code more than they would wish, but if so let me know.
--
ken
http://myriadicity.net
On Sun, Dec 21, 2008 at 9:49 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> >>> With EPG to supersede PGG, should PGG be marked obsolete?
> >> I would tend to think so, yes, but I'd first like to have the opinion of
> >> PGG author(s) and users. Anybody objects to marking PGG as obsolete?
> > There seems to be no objections. Shall we go ahead marking it obsolete?
>
> Apparently, PGG is still used by allout.el, so we should try and get Ken
> to update his code to use EPG instead before we mark PGG obsolete.
> But please add a node about this to pgg.el (something like "On its way
> to obsolescence, waiting for allout.el to switch to EPG.").
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1621 bytes --]
prev parent reply other threads:[~2008-12-22 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 12:01 Should pgg be mark obsolete? Leo
2008-12-09 21:00 ` Stefan Monnier
2008-12-20 17:41 ` Leo
2008-12-22 2:49 ` Stefan Monnier
2008-12-22 18:22 ` ken manheimer [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cd46e7f0812221022k95ad016k115f3bc47a22cebf@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).