From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Cherrypicking commit e08ed2bae2a8e91c0245259dfcbfdca1d191a119 onto emacs-26 Date: Fri, 16 Mar 2018 15:20:41 +0100 Message-ID: <87muz8rtja.fsf@gmx.de> References: <83zi39p38o.fsf@gnu.org> <83y3itp0ou.fsf@gnu.org> <83tvtgptzz.fsf@gnu.org> <87r2oksakz.fsf@gmx.de> <83sh90p15x.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1521209937 3623 195.159.176.226 (16 Mar 2018 14:18:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 16 Mar 2018 14:18:57 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: p.stephani2@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 16 15:18:53 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ewqC4-0000qH-9Y for ged-emacs-devel@m.gmane.org; Fri, 16 Mar 2018 15:18:52 +0100 Original-Received: from localhost ([::1]:57191 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewqE7-0001El-BF for ged-emacs-devel@m.gmane.org; Fri, 16 Mar 2018 10:20:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60827) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ewqDx-0001Dt-K9 for emacs-devel@gnu.org; Fri, 16 Mar 2018 10:20:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ewqDs-000823-M9 for emacs-devel@gnu.org; Fri, 16 Mar 2018 10:20:49 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:35761) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ewqDs-00081K-CH; Fri, 16 Mar 2018 10:20:44 -0400 Original-Received: from detlef.gmx.de ([213.220.156.85]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MBq8p-1eoM1t25sF-00AmWu; Fri, 16 Mar 2018 15:20:42 +0100 In-Reply-To: <83sh90p15x.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 Mar 2018 16:04:10 +0200") X-Provags-ID: V03:K0:xNN7fsfKxZM9wQAg/mW6NDmOhjCTh1HUNRk7cDA8h5Wvy+h1qn1 55uy/mWHz/at4SEYUJwrDm64gXhhIxNA6TM1Le3XQbsT9e2cWjM0n+22tgPVfTLtx6a/vlj ci8hkIJ6I3NJoVKY0opgzsJBH7Hnd1QA8Zjv3EtRgPmt6PZCMsSiuq7ykTfgDv3XfMP3hG1 tel+Q5BOYY9HiDAenjV8g== X-UI-Out-Filterresults: notjunk:1;V01:K0:NXOEEu/IO7w=:EYbl8UShnGkyfIncO7fiue 6zVa8jJof/LwfGRNQ7KNrumg7G08qLVu82qsKYoCbXbvSirwgvDf8akEqwYuxzmNX5it6AuCm HJSKJt/0rxRDgfYT8ngaurA/i/6fWu7EdsPiIJo2VLB6GnIybG8rXzplGgWdNG14lUzIDQALv dDpSPS/a7K939GPYN37GN6DH9KBbo7C4JyZyGlcGj7bSV3QZQj7P+mqjdYkfyymRHVpk010kP QBYLf9TAunPtUJ5XP35tiZa5KgpTkWARmxDB5egZldkWzwFIhsKOqWQ+1UOYA565hNhTHK/OX HIZyOMMcuESC4qb2kgd/w6k4cmJKRtzRmhOPxy7WtqylgyZjZWEpCVFXGI8FK86MyR9Mxli+I 5ELfX1VKeT5mlaPLrh3XnjqlkuRM/rAXyeTLDg8IvcLicykBZPoTA+Ak4QSHYC8TxVCHkSAlD ExMjM54KNJUeraH3ilei55CBGJObxGnEz8HasWgtqnjCf+TbBp9tE7tW1IwCh5NbnaWLeW1rb CgicX5JuIVCF12Ja57aIgXiqnpkrqsiw9au+vzyx/z+lCzeZ5tmbqRlc2p5Whe/zjvBiikqYf kUJi6MCOVhL1HUsR15G0QR+mND3wwmKYvNrig4ZuvI1c9XHsxRq9BQZughkSzPd4oZsmn9EE0 gJ0sl2KwRZABNOzQRALi1HeeEuMYcKV//TRun69suG+0DUAUdMl1Fj5zJO3DHCryvfmp6Mrzx jTMYMh6L0wMEDcm92nRH/3gR+2SxZ1rPDI1tyfqN+ga3Oz12KgKooYkrVz+r3ZS+sFEsBiew X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.17.22 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:223778 Archived-At: Eli Zaretskii writes: >> This raises the question how we determine patches to be backported to >> Emacs 26.2. I have no idea, but going through all closed bugs and/or all >> commits to the master branch. > > Maybe we should have a file in admin that would list such commits. Or > maybe we should have a special phrase in the commit log message. The latter one is good for errors. See the Version: line we shall add when committing something. Many people, including me, tend to forget it. Another approach would be a staging branch, which collects such backport candidates. Best regards, Michael.