From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Network Security Manager merge time?
Date: Wed, 19 Nov 2014 11:40:55 -0500 [thread overview]
Message-ID: <87lhn7cfe0.fsf@lifelogs.com> (raw)
In-Reply-To: m3r3wzrwia.fsf@stories.gnus.org
On Wed, 19 Nov 2014 17:22:05 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> I think the NSM is basically feature complete (i.e., it does what it's
LMI> supposed to according to our discussions). Bugs probably exist, as in
LMI> all code.
LMI> So perhaps it's time to merge it with trunk? `nsm-security-level' would
LMI> be set to `low', which means that it basically would do nothing.
LMI> But we would get more testing of the basic parts -- that I haven't
LMI> screwed up Emacs too much. And then, after a week or so, we could
LMI> switch it to `medium', which would activate it, and then we'll see what
LMI> people think about the way it works.
Does it deprecate `gnutls-verify-error'? If so, we should note that.
Ted
next prev parent reply other threads:[~2014-11-19 16:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:22 Network Security Manager merge time? Lars Magne Ingebrigtsen
2014-11-19 16:40 ` Ted Zlatanov [this message]
2014-11-19 16:53 ` Lars Magne Ingebrigtsen
2014-11-19 17:30 ` Ted Zlatanov
2014-11-19 17:59 ` Lars Magne Ingebrigtsen
2014-11-19 18:34 ` Ted Zlatanov
2014-11-19 20:00 ` Ivan Shmakov
2014-11-19 20:25 ` Ted Zlatanov
2014-11-19 21:41 ` Ted Zlatanov
2014-11-21 11:29 ` Lars Magne Ingebrigtsen
2014-11-25 14:20 ` Ted Zlatanov
2014-11-25 16:30 ` Lars Magne Ingebrigtsen
2014-11-25 16:46 ` Ted Zlatanov
2014-11-25 17:08 ` Lars Magne Ingebrigtsen
2014-11-25 18:20 ` intrusive changes Ivan Shmakov
2014-11-30 13:51 ` Stefan Monnier
2014-11-30 15:12 ` Ivan Shmakov
2014-11-30 18:07 ` Stefan Monnier
2014-12-02 10:03 ` Ivan Shmakov
2014-12-02 13:50 ` Stefan Monnier
2014-11-19 18:22 ` Network Security Manager merge time? Lars Magne Ingebrigtsen
2014-11-19 20:46 ` Eli Zaretskii
2014-11-19 20:54 ` Lars Magne Ingebrigtsen
2014-11-19 20:58 ` Lars Magne Ingebrigtsen
2014-11-19 21:18 ` Eli Zaretskii
2014-11-20 8:42 ` Lars Magne Ingebrigtsen
2014-11-20 16:16 ` Eli Zaretskii
2014-11-19 17:28 ` Robert Pluim
2014-11-19 17:50 ` Lars Magne Ingebrigtsen
2014-11-19 19:51 ` Robert Pluim
2014-11-19 19:56 ` Lars Magne Ingebrigtsen
2014-11-19 20:06 ` Robert Pluim
2014-11-19 20:20 ` Lars Magne Ingebrigtsen
2014-11-19 20:25 ` Lars Magne Ingebrigtsen
2014-11-19 20:26 ` Robert Pluim
2014-11-19 20:32 ` Lars Magne Ingebrigtsen
2014-11-20 8:00 ` Robert Pluim
2014-11-20 8:43 ` Lars Magne Ingebrigtsen
2014-11-20 9:04 ` Robert Pluim
2014-11-20 10:39 ` Lars Magne Ingebrigtsen
2014-11-20 11:34 ` Robert Pluim
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=87lhn7cfe0.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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.
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).