From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: bidi branch (was: Emacs-23 release branch) Date: Fri, 12 Mar 2010 10:41:54 +0200 Message-ID: <83iq920w4t.fsf@gnu.org> References: <87zl2g24xy.fsf@stupidchicken.com> <83d3zc2iqr.fsf@gnu.org> <87eijsoz6u.fsf@lola.goethe.zz> <833a073kss.fsf@gnu.org> <83wrxj1o92.fsf@gnu.org> <83vdd220yk.fsf@gnu.org> <83r5nq1vox.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1268383386 22409 80.91.229.12 (12 Mar 2010 08:43:06 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 12 Mar 2010 08:43:06 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: James Cloos Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 12 09:43:01 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Nq0SR-0005Ul-C6 for ged-emacs-devel@m.gmane.org; Fri, 12 Mar 2010 09:43:00 +0100 Original-Received: from localhost ([127.0.0.1]:52624 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nq0SN-0004Ch-2e for ged-emacs-devel@m.gmane.org; Fri, 12 Mar 2010 03:42:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nq0Rt-0004Bd-O9 for emacs-devel@gnu.org; Fri, 12 Mar 2010 03:42:25 -0500 Original-Received: from [140.186.70.92] (port=46087 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nq0Rr-0004Aq-2R for emacs-devel@gnu.org; Fri, 12 Mar 2010 03:42:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nq0Rp-00073T-LL for emacs-devel@gnu.org; Fri, 12 Mar 2010 03:42:22 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:48729) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nq0Rp-00073O-DS for emacs-devel@gnu.org; Fri, 12 Mar 2010 03:42:21 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0KZ500400URO3E00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Fri, 12 Mar 2010 10:41:49 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.214.230]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KZ5000G9UTOEL90@a-mtaout20.012.net.il>; Fri, 12 Mar 2010 10:41:49 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:121853 Archived-At: > From: James Cloos > Cc: Stefan Monnier , emacs-devel@gnu.org > Copyright: Copyright 2009 James Cloos > OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 > Date: Thu, 11 Mar 2010 17:19:16 -0500 > > Having the code in the repo in its own branch will be useful for the > rest of us, especially given that you wrote that merging into trunk > would not happen right away. As I explained elsewhere, the bidi code is inactive unless the user customizes a per-buffer variable. So the reasons for not merging into the trunk are not for fear of totally breaking Emacs, and will also delay publishing as a public branch. > And even if it were to happen right away, going through a public branch > may ease future bisection and other anthropological pursuits withing the > repository. Unless someone objects strenuously, I intend to merge all the current history I have on my local branch, without any rebasing or similar tricks that futz with the history. Therefore, bisection will not suffer either way. > In any case, I cannot hurt to make your branch public, and there is no > good reason not to do so within the master repo. I'm still unclear why it makes more sense to have a public branch than to merge with the trunk.