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 23:28:16 +0200 Message-ID: <83y6lzo9e7.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> <83aaygoy90.fsf@gnu.org> <87vdh36d48.fsf@telefonica.net> <831vjrptha.fsf@gnu.org> <87einr63b6.fsf@telefonica.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1258841455 31474 80.91.229.12 (21 Nov 2009 22:10:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 21 Nov 2009 22:10:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 21 23:10:24 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 1NBy9t-0003SB-9V for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 23:10:21 +0100 Original-Received: from localhost ([127.0.0.1]:57779 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBxVK-0001Ka-ML for ged-emacs-devel@m.gmane.org; Sat, 21 Nov 2009 16:28:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NBxVG-0001IS-1e for emacs-devel@gnu.org; Sat, 21 Nov 2009 16:28:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NBxVB-0001Ek-Ed for emacs-devel@gnu.org; Sat, 21 Nov 2009 16:28:21 -0500 Original-Received: from [199.232.76.173] (port=37451 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NBxVB-0001Ea-AH for emacs-devel@gnu.org; Sat, 21 Nov 2009 16:28:17 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:58814) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NBxVA-0005Pw-Qw for emacs-devel@gnu.org; Sat, 21 Nov 2009 16:28:17 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KTH00H00A2Y1000@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Sat, 21 Nov 2009 23:28:15 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTH00FCRAB2YY40@a-mtaout22.012.net.il>; Sat, 21 Nov 2009 23:28:15 +0200 (IST) In-reply-to: <87einr63b6.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:117454 Archived-At: > From: =C3=93scar_Fuentes > Cc: emacs-devel@gnu.org > Date: Sat, 21 Nov 2009 21:17:01 +0100 >=20 > Eli Zaretskii writes: >=20 > >> >> For large compiled projects such as Emacs, the use of feature= branches > >> >> 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? > >>=20 > >> Let's suppose that you want to do some lightweight hacking on a = elisp > >> component of emacs. The `feature branch' workflow says that you = create a > >> new local branch specifically for that: > >>=20 > >> bzr branch path/to/my/local/emacs/mirror fix-bug-3429 > >>=20 > >> and then you edit the .el files. But at some point you want to t= est > >> them, and for that you need an emacs executable. Now, building e= macs is > >> not a fast operation even on a GNU/Linux modern desktop (let's n= ot > >> mention Windows). Hence, even when you start the build right aft= er the > >> feature branch creation, it is possible that you end your modifi= cations > >> before the build ends. This certainly will occur often on slow G= NU/Linux > >> machines and even on fast Windows machines. > > > > I'm not quite sure I understand. Are you talking about bootstrap= ? > > That one indeed can take 30 minutes on Windows. But that's a one= -time > > thing; subsequent builds, when just a handful of files are modifi= ed > > are much faster. It's a rare feature or even a bugfix that needs= only > > one build.=20 >=20 > The newly created feature branch you are working on is a pristine s= et > of versioned files on a new directory. If you want to test your cha= nge, > you need to build the emacs executable, because it is not there. Of course. But building does not take a lot of time, except for the first time, which does a full bootstrap for that branch. > How do you manage your bidi branch right now? Is it a CVS branch on > the Emacs repository or a set of patches that you store on your > machine? It's a CVS checkout of the trunk, with local changes. Each "cvs up" merges the changes on the trunk with my local changes. Since no one is working on the display engine, I had maybe one or two conflicts in several months. It's really not such a big deal, even with CVS. I don't see how any VCS could "shine" in this use-case. Maybe I'm missing something.