From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tino Calancha Newsgroups: gmane.emacs.devel Subject: Should fixes for Bug#23936 go also to emacs-25? Date: Thu, 21 Jul 2016 18:04:06 +0900 (JST) Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Trace: ger.gmane.org 1469094400 27129 80.91.229.3 (21 Jul 2016 09:46:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Jul 2016 09:46:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 21 11:46:30 2016 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 1bQAYl-0000MS-Eq for ged-emacs-devel@m.gmane.org; Thu, 21 Jul 2016 11:46:27 +0200 Original-Received: from localhost ([::1]:39380 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQAYk-0006UR-RG for ged-emacs-devel@m.gmane.org; Thu, 21 Jul 2016 05:46:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQ9tu-0005DZ-EK for emacs-devel@gnu.org; Thu, 21 Jul 2016 05:04:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bQ9tq-0000AO-3m for emacs-devel@gnu.org; Thu, 21 Jul 2016 05:04:13 -0400 Original-Received: from mail-pf0-x22b.google.com ([2607:f8b0:400e:c00::22b]:32799) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bQ9tp-0000AH-Tt for emacs-devel@gnu.org; Thu, 21 Jul 2016 05:04:10 -0400 Original-Received: by mail-pf0-x22b.google.com with SMTP id y134so28502585pfg.0 for ; Thu, 21 Jul 2016 02:04:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:subject:message-id:user-agent:mime-version; bh=avBGPwKQzj53s8kxyzNS3H32y9FcGWBg/ytfsaKsjK8=; b=FotdcwvKrClEYKi44RAnLTnhtbW8/npNbxT1ji/SymUZJ79xlLXD5vH6qJBY59NzGK +NTj4MNRqCVtomndBQtxa07qOMLe1HfyL6X+81JsjFQH/ctZ9rG3usRXIgUthg9/Eejs ImcAjbeV4lAfg4HBVmSrfSRRfXOzisMACEHSElo26Xdd6f/yeoXuHYgmlKq9suWQmCZU F6EbAB5ln11GW4cAUjHPvW3AN7GmYa0KSaDdz+xgb5RUS9VlWyEdEy7YiN1QJ/YGCclO pLACcsaTQXKUhh6y04aQdAxQdh0kbC1X5eQDm3yHgArZLxmwQgg2Iq59Fg9Ym8yu6c4P TS0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:subject:message-id:user-agent :mime-version; bh=avBGPwKQzj53s8kxyzNS3H32y9FcGWBg/ytfsaKsjK8=; b=WM15+qO7MuPwa8ReITNP64ep9jEl2/g9CUTrJzfdGN0MFSG0cqy4S6XjjPG2g+LSg6 uZK6xIz/pn8Lz1NUnqdKXzfmR+kT2ZB8XJQHLn2HmZX9JyidFeXix+tJuThcRS/NK+89 HhIce+7ouMAP+g9qnz8DzfZs06HO+YAJpxWdeW7NufA5FdLU1YoS1G7Esok5JtD3XM7D aZ2yxTRrA1KsrQ4bUtpb9JFHnlHnmeGczu8Nqz0DLpHkxU8xL6kJ6rIq7zaHHGF7fPrj 2pb5uaHEpLS7RDdg1G68xWONCwqFOigwI3eeeWIOKm6+ilY/n5666/mRSQhD8b8mFnvX d3rQ== X-Gm-Message-State: ALyK8tJjm0WwSufHMEWkTbVZbXnErcezfQPuKbKp8AYdWAGO3Q6uI46mxWzCvBJpmFlqdA== X-Received: by 10.98.85.5 with SMTP id j5mr70775422pfb.81.1469091848768; Thu, 21 Jul 2016 02:04:08 -0700 (PDT) Original-Received: from calancha-pc ([103.5.140.148]) by smtp.gmail.com with ESMTPSA id a5sm10340349pfc.89.2016.07.21.02.04.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jul 2016 02:04:08 -0700 (PDT) X-Google-Original-From: Tino Calancha X-X-Sender: calancha@calancha-pc User-Agent: Alpine 2.20 (DEB 67 2015-01-07) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400e:c00::22b X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:205936 Archived-At: Bug#23936 fix several wrong sentences in shell-command, shell-command-on-region doc strings. After pushing the fix to the master branch Noam reminds me that such kind of fixes should go to the release branch. Today i found another wrong sentence in same doc strings (i didn't push the fix for this new issue). It seems i sent email twice to Bug#23936 due to connectivity problems. Sorry. May i ask you what is the procedure here? What branches should get the fix? Thank you