From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Julien Danjou <julien@danjou.info>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r112923: lisp/gnus/sievel-manage.el: fully support STARTTLS, fix bit rot
Date: Tue, 11 Jun 2013 17:05:56 +0900 [thread overview]
Message-ID: <b4mr4g9138b.fsf@jpl.org> (raw)
In-Reply-To: et8v2hyu6g.fsf@fencepost.gnu.org
Glenn Morris wrote:
> I can't see any copyright assignment on file for this author.
> (Ref: http://permalink.gmane.org/gmane.emacs.gnus.general/83132 ?)
I only merged to the Emacs trunk what was done in the Gnus Git
master by Julien Danjou. Julien, hasn't Albert yet signed?
> Katsumi Yamaoka wrote:
>> +2013-06-10 Albert Krewinkel <krewinkel@moltkeplatz.de>
>> +
>> + * sieve-manage.el (sieve-manage-open): work with STARTTLS: shorten
>> + stream managing functions by using open-protocol-stream to do most of
>> + the work. Has the nice benefit of enabling STARTTLS.
>> + Wait for capabilities after STARTTLS: following RFC5804, the server
>> + sends new capabilities after successfully establishing a TLS connection
>> + with the client. The client should update the cached list of
>> + capabilities, but we just ignore the answer for now.
>> + (sieve-manage-network-p, sieve-manage-network-open)
>> + (sieve-manage-starttls-p, sieve-manage-starttls-open)
>> + (sieve-manage-forward, sieve-manage-streams)
>> + (sieve-manage-stream-alist): Remove unneeded functions neither in the
>> + API, nor called by any other function.
>> + Enable Multibyte for SieveManage buffers: The parser won't properly
>> + handle umlauts and line endings unless multibyte is turned on in the
>> + process buffer.
next prev parent reply other threads:[~2013-06-11 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UmJ4U-0000GK-WE@vcs.savannah.gnu.org>
2013-06-11 7:37 ` trunk r112923: lisp/gnus/sievel-manage.el: fully support STARTTLS, fix bit rot Glenn Morris
2013-06-11 8:05 ` Katsumi Yamaoka [this message]
2013-06-11 8:08 ` Julien Danjou
2013-06-11 12:38 ` Stefan Monnier
2013-06-11 12:43 ` Julien Danjou
2013-06-11 15:43 ` Eli Zaretskii
2013-06-11 16:58 ` Glenn Morris
2013-06-11 20:24 ` Julien Danjou
2013-06-11 20:25 ` Glenn Morris
2013-06-12 5:12 ` Richard Stallman
2013-06-11 15:54 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mr4g9138b.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=julien@danjou.info \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).