From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Network security manager Date: Mon, 17 Nov 2014 18:07:43 +0200 Message-ID: <831tp1dd4g.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1416240507 25744 80.91.229.3 (17 Nov 2014 16:08:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Nov 2014 16:08:27 +0000 (UTC) Cc: emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 17 17:08:20 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XqOqg-0002ki-VN for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2014 17:08:19 +0100 Original-Received: from localhost ([::1]:48638 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqOqg-0001FW-Gi for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2014 11:08:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46803) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqOqN-0001Az-Ex for emacs-devel@gnu.org; Mon, 17 Nov 2014 11:08:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XqOqH-0000qC-9w for emacs-devel@gnu.org; Mon, 17 Nov 2014 11:07:59 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:57709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XqOqH-0000pj-2g for emacs-devel@gnu.org; Mon, 17 Nov 2014 11:07:53 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NF600200Y0OJI00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Mon, 17 Nov 2014 18:07:52 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NF6002DQY53JR00@a-mtaout20.012.net.il>; Mon, 17 Nov 2014 18:07:51 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177436 Archived-At: > From: Lars Magne Ingebrigtsen > Date: Mon, 17 Nov 2014 13:46:59 +0100 > > I plan on starting to implement the Emacs network security manager soon > (hopefully this evening), but I was wondering whether to do it on a > public feature branch or on the trunk. What is an "Emacs network security manager"? What will it manage? Whether to develop on a separate branch depends on how invasive are the changes in parts that are not turned off/bypassed when that variable of yours is off.