From: Simon Josefsson <simon@josefsson.org>
To: Elias Oltmanns <eo@nebensachen.de>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [Patch] Make tls.el support certificate verification
Date: Tue, 25 Sep 2007 16:42:54 +0200 [thread overview]
Message-ID: <87ps063ixd.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <v9bqbst4fe.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 24 Sep 2007 18:27:01 +0200")
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Mon, Sep 24 2007, Simon Josefsson wrote:
>
>> I think it should be installed in both CVS's, although perhaps
>> tls.el should be removed from the Gnus repository. Others on the
>> ding list, which Emacs version does Gnus in CVS require?
>
> See (info "(gnus)Emacsen") or...
>
> ,----[ (info "(gnus-coding)Gnus Coding Style") ]
> | 1.2 Compatibility
> | =================
> |
> | No Gnus and Gnus 5.10.10 and up should work on:
> | * Emacs 21.1 and up.
> |
> | * XEmacs 21.4 and up.
> |
> | Gnus 5.10.8 and below should work on:
> | * Emacs 20.7 and up.
> |
> | * XEmacs 21.1 and up.
> `----
>
>> If that emacs version has tls.el, I'm not sure it makes sense to
>> keep tls.el in the Gnus repository.
>
> Emacs 21 doesn't have it, so I think we should keep it.
Right, thanks. Let's wait for copyright papers and then apply the patch
in both CVS's.
/Simon
next prev parent reply other threads:[~2007-09-25 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 23:08 Elias Oltmanns
2007-09-24 7:12 ` Simon Josefsson
2007-09-24 16:27 ` Reiner Steib
2007-09-25 14:42 ` Simon Josefsson [this message]
2007-11-08 18:44 ` Elias Oltmanns
2007-11-08 19:52 ` Reiner Steib
2007-11-16 17:22 ` Elias Oltmanns
2007-11-16 22:38 ` Reiner Steib
2007-11-16 23:07 ` Elias Oltmanns
2007-11-24 21:31 ` Reiner Steib
2007-11-25 0:35 ` Elias Oltmanns
2007-11-25 14:18 ` Reiner Steib
2007-11-26 14:47 ` Simon Josefsson
2007-11-27 11:10 ` Elias Oltmanns
2007-11-28 22:05 ` Reiner Steib
2007-11-28 22:08 ` Coding conventions (was: [Patch] Make tls.el support certificate verification) 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=87ps063ixd.fsf@mocca.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=eo@nebensachen.de \
/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).