From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "ken manheimer" Newsgroups: gmane.emacs.devel Subject: Re: Should pgg be mark obsolete? Date: Mon, 22 Dec 2008 13:22:21 -0500 Message-ID: <2cd46e7f0812221022k95ad016k115f3bc47a22cebf@mail.gmail.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_83150_30998777.1229970141633" X-Trace: ger.gmane.org 1229970172 31495 80.91.229.12 (22 Dec 2008 18:22:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 22 Dec 2008 18:22:52 +0000 (UTC) Cc: Leo , emacs-devel@gnu.org To: "Stefan Monnier" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 22 19:23:57 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LEpRY-0007hM-5b for ged-emacs-devel@m.gmane.org; Mon, 22 Dec 2008 19:23:53 +0100 Original-Received: from localhost ([127.0.0.1]:41776 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LEpQK-0005qm-Vk for ged-emacs-devel@m.gmane.org; Mon, 22 Dec 2008 13:22:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LEpQA-0005lE-Al for emacs-devel@gnu.org; Mon, 22 Dec 2008 13:22:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LEpQ9-0005kV-1N for emacs-devel@gnu.org; Mon, 22 Dec 2008 13:22:25 -0500 Original-Received: from [199.232.76.173] (port=46495 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LEpQ8-0005kN-Hl for emacs-devel@gnu.org; Mon, 22 Dec 2008 13:22:24 -0500 Original-Received: from fg-out-1718.google.com ([72.14.220.153]:29992) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LEpQ8-0007b2-2M for emacs-devel@gnu.org; Mon, 22 Dec 2008 13:22:24 -0500 Original-Received: by fg-out-1718.google.com with SMTP id l26so931917fgb.30 for ; Mon, 22 Dec 2008 10:22:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=0HKCBFYR9f15lDGVblE0YBpTHa1pTYEURxEmWLtMZ7Y=; b=xA4lem2mA6vWx6NDmTqr8RuO0YC+wDlvyr/HDuxk1voxQXLt7AjEWEmOPEreApUKOc vRJfEy2l7QCSgYp+SrrZl0gsKZcXsb9dxmIhiUmRmIn824VEUMn2cDS7C9z/mjIYOkXs l7hNyQ6L0gmyCDl6s6lmCr9p9tqMhABsCZUYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=wdRRimJPqIiWl3pPLmllXELMiSpYUHTcHbhhAc4kDu1h5Iox9nfaL8O+N05SQyMD/9 5KdFXk84dlq7uQxQUXou9XJEVJXRDwn2LGBVmwa7R2Toi+RpvhyrWxpmu8FS82v9BADD DPARpGAwOphNDOEEdA/PE28sbNh2GXQfayT6k= Original-Received: by 10.103.221.5 with SMTP id y5mr2408443muq.66.1229970141638; Mon, 22 Dec 2008 10:22:21 -0800 (PST) Original-Received: by 10.103.90.11 with HTTP; Mon, 22 Dec 2008 10:22:21 -0800 (PST) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107186 Archived-At: ------=_Part_83150_30998777.1229970141633 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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 > ------=_Part_83150_30998777.1229970141633 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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

------=_Part_83150_30998777.1229970141633--