From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thierry Volpiatto Newsgroups: gmane.emacs.devel Subject: Re: patch vs. overwrite in bzr Date: Wed, 04 Apr 2012 19:53:53 +0200 Message-ID: <871uo31iz2.fsf@gmail.com> References: <87k42cwys8.fsf@gnu.org> <87limhuldm.fsf@gnu.org> <871uo7g4j6.fsf@gnu.org> <87iphjhbm8.fsf@wanadoo.es> <87398lgrat.fsf_-_@niu.edu> <871uo5c7r0.fsf@wanadoo.es> <87pqbpj5j3.fsf@altern.org> <87aa2szgig.fsf@gnu.org> <87ehs4yrhz.fsf@gnu.org> <87vclg804u.fsf@gmx.de> <87ehs3sxm1.fsf@gmail.com> <83iphfctk5.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1333562540 13161 80.91.229.3 (4 Apr 2012 18:02:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 4 Apr 2012 18:02:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 04 20:02:19 2012 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 1SFUXD-0001kh-Df for ged-emacs-devel@m.gmane.org; Wed, 04 Apr 2012 20:02:19 +0200 Original-Received: from localhost ([::1]:36780 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SFUPV-0006eh-VB for ged-emacs-devel@m.gmane.org; Wed, 04 Apr 2012 13:54:21 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:53187) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SFUPO-0006e7-Vm for emacs-devel@gnu.org; Wed, 04 Apr 2012 13:54:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SFUPK-0000M0-3s for emacs-devel@gnu.org; Wed, 04 Apr 2012 13:54:14 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:49367) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SFUPJ-0000Lt-T9 for emacs-devel@gnu.org; Wed, 04 Apr 2012 13:54:10 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SFUPH-0005T8-AV for emacs-devel@gnu.org; Wed, 04 Apr 2012 19:54:07 +0200 Original-Received: from lbe83-2-78-243-104-167.fbx.proxad.net ([78.243.104.167]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Apr 2012 19:54:07 +0200 Original-Received: from thierry.volpiatto by lbe83-2-78-243-104-167.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Apr 2012 19:54:07 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lbe83-2-78-243-104-167.fbx.proxad.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux) Cancel-Lock: sha1:dmAZdZx3sKwRW4MTqsUnSFEezn4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:149380 Archived-At: Eli Zaretskii writes: >> From: Thierry Volpiatto >> Date: Wed, 04 Apr 2012 10:35:34 +0200 >> >> I never understood why Emacs have not a developing branch to continue >> developing new features during the feature freeze. > > Read the archives for past discussions of this issue, and you will > understand. The reason is insufficient resources. It takes a > significant effort to run a pretest, triage the bugs and fix important > ones, update the manuals, etc. The extremely small number of core > maintainers does not leave resources to overview both the branch and > the trunk, as long as there's lots of work on each one of them. You should not have to overview the dev branch, only the trunk and merge regularly it in the dev branch. You would have only to review the patches before applying to dev branch, but that's what you already do I think. The difference is just that actually you say, yes patch is ok we will apply it after feature freeze. Instead you would just have to apply if ok. > People who want this to change should volunteer to do the tasks that > are needed to be done for the pretest and release. Then 2 things will > happen: (1) there will be more people who can take a responsibility > for a release, thus freeing more time for the head maintainers to take > care of the trunk; and (2) the number of people who are familiar with > Emacs enough to become core maintainers will also grow. > >> I think Emacs lost a lot a new features during this process, especially >> from contributors that send patches; most patches are lost or >> are unusable after several months of modifications in trunk. > > If you use bzr or any other dVCS, you can simply put your changes on a > branch or even a shelf, and then when the time comes to push them, you > will have much less trouble than you think. Modern VCSes do a very > good job at merging. I know this, I use patches that I can pop and push again after pulling last changes upstream. -- Thierry Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997