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: bzr repository ready? Date: Sat, 21 Nov 2009 14:31:23 +0200 Message-ID: <83aaygoy90.fsf@gnu.org> References: <87639fr3w7.fsf@red-bean.com> <87vdhfpil2.fsf@red-bean.com> <87einvxy9c.fsf@red-bean.com> <20091118230952.GB908@muc.de> <87my2jw05z.fsf@red-bean.com> <83skc9pbf7.fsf@gnu.org> <87iqd5vw5n.fsf@red-bean.com> <877htl53tc.fsf@telefonica.net> <87ws1ku7zd.fsf@red-bean.com> <87hbso4s13.fsf@telefonica.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1258806724 25353 80.91.229.12 (21 Nov 2009 12:32:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Nov 2009 12:32:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?windows-1252?Q?=D3scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 21 13:31:57 2009 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.50) id 1NBp89-0003rl-C0 for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 13:31:57 +0100 Original-Received: from localhost ([127.0.0.1]:51944 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBp88-00015H-HF for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 07:31:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBp7i-0000pk-9z for emacs-devel@gnu.org; Sat, 21 Nov 2009 07:31:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBp7d-0000nN-2M for emacs-devel@gnu.org; Sat, 21 Nov 2009 07:31:29 -0500 Original-Received: from [199.232.76.173] (port=46340 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBp7c-0000nI-TF for emacs-devel@gnu.org; Sat, 21 Nov 2009 07:31:24 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:58284) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBp7c-0004HM-DP for emacs-devel@gnu.org; Sat, 21 Nov 2009 07:31:24 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0KTG00800KQ5JC00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Sat, 21 Nov 2009 14:31:23 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTG007EJLGA1R50@a-mtaout20.012.net.il>; Sat, 21 Nov 2009 14:31:23 +0200 (IST) In-reply-to: <87hbso4s13.fsf@telefonica.net> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.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:117436 Archived-At: > From: =D3scar_Fuentes > Date: Sat, 21 Nov 2009 01:53:44 +0100 >=20 > For large compiled projects such as Emacs, the use of feature branc= hes > is not that great. First, building takes a long time. Why does the building take a long time in that case? > Second, it imposes a large penalty on those who just want to hack > some elisp. What penalty is that? > Maybe a system based on `bzr switch' is the solution for Emacs, > although it is not so simple to understand as feature branches. For > the diehard CVS users, beginning with a single work branch is the > solution. `bzr shelve' would help them I'd appreciate some more details on that. It's hard to make up your mind about the usage patterns with so many new factors being introduced in ever sentence without any explanations. (And yes, I di= d read the Bazaar User Reference for these two commands, but it's just awful: "bzr shelve" does not describe its argument FILE, "bzr switch" does not tell what is its argument TO_LOCATION, etc. The User Guide helps a bit, but you cannot search in it, at least not in the on-line version.)