From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines Date: Thu, 03 Nov 2011 02:29:15 +0100 Message-ID: <8762j2dmdw.fsf@gnu.org> References: <87pqhrih3s.fsf@gmail.com> <87zkgvfhra.fsf@gmail.com> <2127.1319148505@alphaville.dokosmarshall.org> <87vcrjfgt1.fsf@gmail.com> <80sjmmvm60.fsf@somewhere.org> <4EA129DB.4070006@christianmoe.com> <8762ji5jr6.fsf@gmail.com> <4EA1D4F9.5010302@christianmoe.com> <4ea1de9c.67b4ec0a.553d.122a@mx.google.com> <87aa8t10np.fsf@gmail.com> <4ea5a95b.059dec0a.606e.0c92@mx.google.com> <874nypkn6y.fsf@gmail.com> <87obwwkia5.fsf@gmail.com> <87boswk4vj.fsf@gmail.com> <8627.1320157576@alphaville.dokosmarshall.org> <9991.1320159724@alphaville.dokosmarshall.org> <87hb2nj2ic.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:59759) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLm6Q-0004Yc-US for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 21:28:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLm6P-0007zC-J3 for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 21:28:22 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:62616) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLm6P-0007z7-CR for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 21:28:21 -0400 Received: by wwe3 with SMTP id 3so895562wwe.30 for ; Wed, 02 Nov 2011 18:28:20 -0700 (PDT) In-Reply-To: (Brian Wightman's message of "Wed, 2 Nov 2011 07:57:36 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Brian Wightman Cc: emacs-orgmode@gnu.org Hi Brian, Brian Wightman writes: > Given that a common recommendation for a bug fix is to 'try commit > blah blah blah', would it make sense to have bug fixes go onto a > 'maint' branch (as well as master), and new features / changed > features stay on the master branch? Yes, this makes sense, and this has already been suggested. The reason why I'm not using such a scheme is 1) pure laziness and 2) the fact that the current git scheme is "good enough". But it might not be good enough for long, and perhaps future maintainers will not be as lazy as I am wrt this. Thanks for the suggestion, -- Bastien