Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: ding@gnus.org,  Miles Bader <miles@gnu.org>
Subject: Re: pgg-gpg doesn't work at all [fix included]
Date: Sun, 29 Jul 2007 03:18:35 +0900	[thread overview]
Message-ID: <4e687c1c-a602-4248-a49f-535fa0372646@well-done.deisui.org> (raw)
In-Reply-To: <v9lkd0zh74.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 28 Jul 2007 17:22:23 +0200")

>>>>> In <v9lkd0zh74.fsf@marauder.physik.uni-ulm.de> 
>>>>>	Reiner Steib <reinersteib+gmane@imap.cc> wrote:
> >> Reverting PGG in the Gnus trunk to the version in v5-10 is fine with
> > 3. Including EasyPG to the Emacs CVS (not to the Gnus CVS).

> Why "not to the Gnus CVS"?

Because EasyPG is not a helper program of Gnus (as I said again and
again).  Indeed EasyPG contains a functions which can be used to
implement sign and encryption support in Gnus though, most users use
other features such as transparent encryption.

> We want to sync Gnus trunk with Emacs trunk.  If EasyPG should become
> the default sign and encryption support in Gnus (obsoleting PGG) ---
> and as I understand this is your suggestion ---, we should have the
> EasyPG package included in both Gnus trunk and Emacs trunk.

Why the repository location matters?  I don't want to import EasyPG to
Gnus CVS.

> > While Miles seems to be only interested in 1 & 2, I suggest that 3
> > should be done before 2 for a smooth transition.

> Given that with 1 we try to get rid of one variant of PGG/Gnus code, I
> don't quite understand your concerns (about 1a?).

1a.

> 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.

Sure.

Regards,
-- 
Daiki Ueno



  reply	other threads:[~2007-07-28 18:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 10:15 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 [this message]
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
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=4e687c1c-a602-4248-a49f-535fa0372646@well-done.deisui.org \
    --to=ueno@unixuser.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=miles@gnu.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).