From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.devel Subject: CONTRIBUTE and where to commit bug fixes Date: Fri, 07 Sep 2018 02:56:23 +0200 Message-ID: <87pnxqyvk8.fsf@web.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1536281678 16038 195.159.176.226 (7 Sep 2018 00:54:38 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 7 Sep 2018 00:54:38 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: Emacs Development Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 07 02:54:34 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 1fy52e-00043N-Af for ged-emacs-devel@m.gmane.org; Fri, 07 Sep 2018 02:54:32 +0200 Original-Received: from localhost ([::1]:35996 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fy54k-0005Bu-Am for ged-emacs-devel@m.gmane.org; Thu, 06 Sep 2018 20:56:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fy54c-0005Bm-NQ for emacs-devel@gnu.org; Thu, 06 Sep 2018 20:56:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fy54V-0003GD-7o for emacs-devel@gnu.org; Thu, 06 Sep 2018 20:56:33 -0400 Original-Received: from mout.web.de ([212.227.17.12]:46345) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fy54U-0003CP-Dy for emacs-devel@gnu.org; Thu, 06 Sep 2018 20:56:26 -0400 Original-Received: from drachen.dragon ([94.216.13.226]) by smtp.web.de (mrweb102 [213.165.67.124]) with ESMTPSA (Nemesis) id 0M40zO-1fgpMr3kCw-00rcQU; Fri, 07 Sep 2018 02:56:24 +0200 X-Provags-ID: V03:K1:caniUWnKrdvd26I6CINwqLrEPyPDSXeixtCstQ2t96o6N+JWCsa mvgHfjFqlwlSYixof9K/+s0XALnWY8dmFz8E2/qsHGbmwaCWbA6r9eRjN1yLycChTW8WJyF iZhgKHlm3WO7d6z/Q484QVXfHLrY74O+V4EnHof0iBx4mUcrso6IDilgirWcVUj4v9ygDDC a9d9C42ntb9CzcNpXv4gw== X-UI-Out-Filterresults: notjunk:1;V01:K0:jAeU3QzHCUU=:GVLADCrSsggvURbTBcxULL gD5X3fE6a+ZvoD9QJZtZvBNM2gbUe5FDMGgPPL3Jn2HWNnVlFFEtv1wIAoksLwlSftLsEIjFs FNvfZUJ4yMQdkcTGVpg7E8nRBNl8hUpgSOoGZ+1B2ikyt1JjnjSUP04KtRq3xrgFX+MCMgC2k G9Rbd5i/4CK9lWIq9Ftr5gwRTEsvptiinDimv88eH1b3VPEh2MM8stHctJlune0dbtxU5YC7/ D4YNPEU2LgpMlLGoUXNFEiLdUdIwL1TewuumfAxqNax6xQ08Kw8isHu+19FL3maaWNYENandu PyQORYzL4t5wQjlUH8Gz71Wpl0qcxiCFDFVzXo2qLldZo8pxVuj7oQPG1AvtzPdmEWrG2d6Om o6lFIOPJXE2H/D1YVaA3dxJuT+AFk+dQvFMlXzL9IzzE/Erogei4+x17QfJIej5LjfaxcNYae 8z/m9FZ7O1Rs9KeONO6JUUmYbAPgYPJDMd6hhr8msx4XJ93oioQ7Coa0wbugwR2YY/Z/GacWc OfeyCVk0sSA4BbaxJfGQTLfw90EEdWGqEUAwcOXwR5yu0xXkCDVhKWsDgZ9Z1eEZKIBgEgeiF NGttR0D2tgZyBcUdO2kzzfcQ4pjc2QMTzX2oDSf1nIr4wxTr07k5mwooUdPzld2My7Z6uQ2lN kavhXoMLEiNYZmHq5Zuv4pk/yL9VZJ1iW+bk6IR51cRP0kV4scmLt0wmzUQ1uWEd7FUkuW+Mn MBWAFhiQ1cYxDEI9dGK+6yX3aioyVCvh4T+tyEGLOkxSfwJRLTgOdPrG5GDMpHIyNsAvvFA5 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.12 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:229363 Archived-At: Hello, As an occasional contributor I'm often unsure about to which branch a bug fix or change should be committed to. In CONTRIBUTE we have this paragraph: | If you are fixing a bug that exists in the current release, be sure to | commit it to the release branch; it will be merged to the master | branch later by the gitmerge function. but that's obviously not always true: depending on the release cycle, only fixes for bugs that where introduced in the last release are accepted, or even less. And if a fix is not ok for the release branch in a moment, should it go to master, or should it just wait until later? So - could we enhance the quoted paragraph? As it is I find it misleading. How can I find out which fixes are acceptable for the release branch at any moment without asking every time? I'm already following emacs-dev but still sometimes find difficult to answer this question. I couldn't exactly say what the current policy is for example. Thanks, Michael.