From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Hans BKK Newsgroups: gmane.emacs.help Subject: Re: viper-mode C-[ behavior change in Emacs 24.4 Date: Fri, 8 Aug 2014 07:35:50 -0700 (PDT) Message-ID: <813c3595-beb1-4bc7-8a24-b7e30bc5ac01@googlegroups.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1407508827 11718 80.91.229.3 (8 Aug 2014 14:40:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Aug 2014 14:40:27 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Aug 08 16:40:21 2014 Return-path: Envelope-to: geh-help-gnu-emacs@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 1XFlL9-0003Pn-BS for geh-help-gnu-emacs@m.gmane.org; Fri, 08 Aug 2014 16:40:19 +0200 Original-Received: from localhost ([::1]:51480 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XFlL9-0004Ic-0A for geh-help-gnu-emacs@m.gmane.org; Fri, 08 Aug 2014 10:40:19 -0400 X-Received: by 10.66.252.6 with SMTP id zo6mr3925305pac.40.1407508551026; Fri, 08 Aug 2014 07:35:51 -0700 (PDT) X-Received: by 10.182.165.69 with SMTP id yw5mr4058obb.40.1407508550758; Fri, 08 Aug 2014 07:35:50 -0700 (PDT) Original-Path: usenet.stanford.edu!h18no10232602igc.0!news-out.google.com!px9ni588igc.0!nntp.google.com!h18no16221190igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2602:306:334f:a5e0:1c7e:27aa:bf7e:4144; posting-account=IUdGewoAAACF9WtA3i8stuVyXNk2FqaH Original-NNTP-Posting-Host: 2602:306:334f:a5e0:1c7e:27aa:bf7e:4144 User-Agent: G2/1.0 Injection-Date: Fri, 08 Aug 2014 14:35:50 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:206863 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:99138 Archived-At: > "in production" (still unclear to me exactly what that means)=20 These issues aren't so significant in environments where the user maintains= their own system, but critical in organizations where a small staff is res= ponsible for hundreds or thousands of hosts, and users are usually not allo= wed to modify their system. "Production" systems are ones that are relied upon for critical operations,= those that incur a significant cost if they stop working. These are often = set up to run for years without any significant changes in order to minimiz= e downtime and maintenance costs. Doesn't have to be a multi-user host either, the CEO's personal desktop is = usually treated as a critical "production" system. To distinguish from "testing" machines or other hosts where downtime is NBD= . Marking a release (package, repo or distro) as "stable" usually implies the= components-collection has gone through longer (over time) and more thoroug= h (more people and platforms, in combination with more variables) TESTING. = Newer releases are by that definition inherently "unstable". Significant security issues are usually the only exception, their fixes oft= en "backported" to the older releases.