From: Simon Josefsson <simon@josefsson.org>
To: ding@gnus.org
Cc: Daiki Ueno <ueno@unixuser.org>, Miles Bader <miles@gnu.org>
Subject: Re: Reverting PGG to v5-10 code base on the trunk
Date: Wed, 03 Oct 2007 16:17:08 +0200 [thread overview]
Message-ID: <87ir5ob7vf.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <v9lkakxps9.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 03 Oct 2007 15:59:18 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Fri, Aug 31 2007, Reiner Steib wrote:
>
>> On Fri, Aug 31 2007, Reiner Steib wrote:
>>
>>> [Quoting added:]
>>>>> > 1. Reverting PGG in the Gnus trunk to the version in v5-10.
>>>>> > 1a. Fixing bugs caused by 1. and testing...
>>>>> > 2. Synch'ing Gnus in the Emacs CVS to the Gnus trunk.
>>>>> > 3. Including EasyPG to the Emacs CVS (not to the Gnus CVS).
>> [...]
>>>>> Getting through the copyright process may take quite a long time, so I
>>>>> don't think we should delay items 1, 1a and 2 while waiting for (or
>>>>> working on) 3.
> [...]
>> Would someone like to work on this? I.e. compare v5-10/lisp/pgg*.el
>> with trunk/lisp/pgg*.el and sync the files (direction: v5-10 -->
>> trunk). The use of `password.el' in the trunk might need some
>> attention. I don't know what is the right thing to do there. The
>> diff (cvs diff -u -r HEAD -r v5-10 pgg*.el) is only 13 hunks
>> (unrelated GPLv3 changes excluded), so it should be a feasible job.
>> Probably Daiki Ueno or Simon Josefsson are able to answer specific
>> questions.
>
> Simon, the code related to password.el in the trunk was added by you.
> Could you please comment if reverting those will cause problems?
I don't remember, sorry. The code was added to clean up and improve the
password handling in PGG. It may be that some features of password.el
were not available before.
> I have reverted PGG to the version in v5-10 now. Please test and
> report problems.
I think that is the best approach.
/Simon
next prev parent reply other threads:[~2007-10-03 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 10:15 pgg-gpg doesn't work at all [fix included] Michael Sperber
2007-07-25 10:44 ` Daiki Ueno
2007-07-25 10:55 ` Michael Sperber
2007-07-25 12:18 ` Sascha Wilde
2007-07-25 12:40 ` Daiki Ueno
2007-07-25 17:40 ` Leo
2007-07-26 0:21 ` Miles Bader
2007-07-26 0:43 ` Daiki Ueno
2007-07-26 1:00 ` Miles Bader
2007-07-26 21:16 ` Reiner Steib
2007-07-26 23:53 ` Daiki Ueno
2007-07-28 15:22 ` Reiner Steib
2007-07-28 18:18 ` Daiki Ueno
2007-07-29 8:03 ` Daiki Ueno
2007-08-31 9:33 ` PGG and EasyPG (was: pgg-gpg doesn't work at all [fix included]) Reiner Steib
2007-08-31 10:21 ` Reverting PGG to v5-10 code base on the trunk (was: PGG and EasyPG) Reiner Steib
2007-10-03 13:59 ` Reverting PGG to v5-10 code base on the trunk Reiner Steib
2007-10-03 14:17 ` Simon Josefsson [this message]
2007-08-31 14:13 ` PGG and EasyPG (was: pgg-gpg doesn't work at all [fix included]) Daiki Ueno
2007-09-03 21:36 ` Leo
2007-09-04 7:00 ` Daiki Ueno
2007-09-04 7:20 ` Leo
2007-07-26 21:27 ` pgg-gpg doesn't work at all [fix included] Reiner Steib
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=87ir5ob7vf.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=miles@gnu.org \
--cc=ueno@unixuser.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;
as well as URLs for NNTP newsgroup(s).