Re: [Patch] Make tls.el support certificate verification

[Reiner Steib <reinersteib+gmane@imap.cc>]

On Fri, Nov 16 2007, Elias Oltmanns wrote:

> Well, I sent ChangeLog entries a week ago (see [1] and [2]) but nothing
> has shown up in cvs yet.  

Sorry for the delay, I didn't have a change do commit your changes
during the past week (I'm not at home and I don't have a reasonable
internet connection at the moment).

> BTW: It has happened several times in the past that messages I sent to
> the ding list went (seemingly) unnoticed.  

I have read your messages.  For tls.el, I hoped that Simon or someone
else can comment as I'm not familiar with it.  Similar for your agent
related patches (I don't even use the agent).

> This is particularly annoying if the message actually contains a
> ready made patch to fix a bug and all I'm asking for is to review
> the patch and tell me what's wrong with it so it can be committed
> eventually.  

If you don't get responses, please feel free to remind us about the
issue.  (Before your papers had been arrived, we couldn't install your
patches.)

> Curiously enough, the message I finally got a response to (the one
> that started this thread) was about adding a new feature rather than
> fixing a bug in existing code.  It also strikes me that this message
> went to both, the ding list as well as emacs-devel.

I don't think there is a strong correlation.

> This makes me wonder whether I should generally send patches to the
> emacs-devel list rather than the ding list even if they concern the
> gnus trunk.  

Now that the Gnus trunk is also in Emacs trunk you may send it
emacs-devel in this case as well.  But please keep ding copied too.

> Or should I just Cc one of the Gnus developers instead?  In that
> case, is there a source where I can see who is maintaining which
> part of Gnus?

You may Cc the maintainer listed in the file.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/