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: patch vs. overwrite in bzr Date: Fri, 06 Apr 2012 12:57:40 +0300 Message-ID: <838vi9b2sr.fsf@gnu.org> References: <87k42cwys8.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> <83k41vctyg.fsf@gnu.org> <83aa2rcnww.fsf@gnu.org> <8362dedgcb.fsf@gnu.org> <87zkapi7qe.fsf@gnu.org> <83iphdb6dp.fsf@gnu.org> <878vi9gqst.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: dough.gmane.org 1333706785 1222 80.91.229.3 (6 Apr 2012 10:06:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 6 Apr 2012 10:06:25 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca To: Bastien Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 06 12:06:24 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 1SG63j-0007dy-LC for ged-emacs-devel@m.gmane.org; Fri, 06 Apr 2012 12:06:23 +0200 Original-Received: from localhost ([::1]:44991 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG5wP-0003xh-9L for ged-emacs-devel@m.gmane.org; Fri, 06 Apr 2012 05:58:49 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:40966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG5wL-0003vx-P6 for emacs-devel@gnu.org; Fri, 06 Apr 2012 05:58:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SG5wK-0002hi-0Y for emacs-devel@gnu.org; Fri, 06 Apr 2012 05:58:45 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:62737) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SG5wH-0002ge-Ip; Fri, 06 Apr 2012 05:58:41 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0M2100L00YC2X700@a-mtaout22.012.net.il>; Fri, 06 Apr 2012 12:58:25 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.229.252.114]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0M2100L95YD8CIF0@a-mtaout22.012.net.il>; Fri, 06 Apr 2012 12:58:25 +0300 (IDT) In-reply-to: <878vi9gqst.fsf@gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 80.179.55.172 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:149422 Archived-At: > From: Bastien > Cc: rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Fri, 06 Apr 2012 11:20:18 +0200 > > Eli Zaretskii writes: > > >> From: Bastien > >> Cc: Stefan Monnier , eliz@gnu.org, emacs-devel@gnu.org > >> Date: Fri, 06 Apr 2012 10:29:13 +0200 > >> > >> Regular Org testers don't want to rebuild Emacs each time they have > >> to test a new feature in Org. > > > > Why would they need to do that? Org is not preloaded into Emacs, so > > all you need is compile the new Org files and perhaps restart the > > Emacs session, but not rebuild Emacs. > > Right. But there are other problems. > > - Updating to the latest Org via `bzr update' would take longer compared > to the current `git pull' (several factors here...) Like what? And how much faster is "faster"? I believe this is just the general git-preference issue, which has nothing to do with "faster". > - Some people don't have access to their Emacs installation (at work, > for example) and still want the latest Org. Well, that's what site-lisp and/or load-path are for, right? That's how those users install Org right now anyway, I believe. They can continue doing that if Org were to be maintained as part of the Emacs repository. > And surely more. In any case, I'm all in favor of having the most > recent Org in Emacs trunk regularily, but migrating the development > of Org from the separate git repo to Emacs bzr repo is a no-go. I understand, and I think this is the _only_ real issue involved.