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: Mon, 23 Nov 2009 21:36:47 +0200 Message-ID: <83d439nicw.fsf@gnu.org> References: <87zl6vskq0.fsf@red-bean.com> <874op07kb0.fsf@red-bean.com> <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> <87vdh29lfo.fsf@red-bean.com> <83k4xhoo0n.fsf@gnu.org> <87my2dhlko.fsf@telefonica.net> <87r5rpsnfw.fsf@uwakimon.sk.tsukuba.ac.jp> <87einpf74m.fsf@uwakimon.sk.tsukuba.ac.jp> 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 1259005027 27189 80.91.229.12 (23 Nov 2009 19:37:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Nov 2009 19:37:07 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 23 20:37:00 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 1NCeiX-0005mW-9I for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 20:36:57 +0100 Original-Received: from localhost ([127.0.0.1]:38870 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCeiW-0007NH-Ro for ged-emacs-devel@m.gmane.org; Mon, 23 Nov 2009 14:36:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCeiR-0007N3-2q for emacs-devel@gnu.org; Mon, 23 Nov 2009 14:36:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCeiM-0007MS-GU for emacs-devel@gnu.org; Mon, 23 Nov 2009 14:36:50 -0500 Original-Received: from [199.232.76.173] (port=52870 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCeiM-0007MP-Bd for emacs-devel@gnu.org; Mon, 23 Nov 2009 14:36:46 -0500 Original-Received: from mtaout21.012.net.il ([80.179.55.169]:35884) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCeiL-00057S-LR for emacs-devel@gnu.org; Mon, 23 Nov 2009 14:36:45 -0500 Original-Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0KTK00A00UBQXH00@a-mtaout21.012.net.il> for emacs-devel@gnu.org; Mon, 23 Nov 2009 21:36:44 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KTK007AAUH61WC0@a-mtaout21.012.net.il>; Mon, 23 Nov 2009 21:36:43 +0200 (IST) In-reply-to: <87einpf74m.fsf@uwakimon.sk.tsukuba.ac.jp> 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:117612 Archived-At: > From: "Stephen J. Turnbull" > Date: Tue, 24 Nov 2009 03:06:33 +0900 > Cc: emacs-devel@gnu.org >=20 > I'm reasonably satisfied that it would not be a waste of your time = to > review it at this point (and I'm looking forward to Eli's opinion, = I'm > hoping he'll find it useful). It is very useful, thanks. I have a few comments, mostly editorial, and some questions: If you are a committer, you will want to use a bzr+ssh URL instead= : bzr+ssh://bzr.savannah.gnu.org/sources/emacs/trunk. Doesn't this URL require a savannah username somewhere in it? This first checkout may take many minutes. It's unclear to what command this refers: none of them mentioned any "checkouts". If there are other branches you=E2=80=99d like to mirror ... Question: doesn't the local repository we just created include all th= e branches anyway? Didn't someone say that the repository allows working off-line? if so, it should include all the branches in the master repository, no? Compared to CVS, these branches are lightweight =E2=80=94 it doesn= =E2=80=99t cost much to create them, as they=E2=80=99re all sharing storage in the repo= sitory, and they can=E2=80=99t bother anyone else. However, there is one =E2= =80=9Cweighty=E2=80=9D aspect: the source tree itself, which takes time to check out. Even more important, there will be no build products in the tree. make boots= trap takes an annoying amount of time. That=E2=80=99s why we recommend = that for small changes you use a dedicated branch. Once you=E2=80=99ve boot= strapped the build, the update, build, and commit elements of the update-edit-build-test-commit cycle are all very fast. This is confusing and looks like a merge of 2 different narratives. Is ``dedicated branch'' what is later described as ``feature branches'' or something else? If the source tree is ``weighty'', the= n why are the branches ``lightweight''? Why is it important that there will be no build products in the tree? etc. etc. Please consider rewriting this paragraph. Once you have completed the task, you=E2=80=99ll want to send it upstream. You do this just as you would for a quick fix ... What about branches in the master repository? Unless I'm missing something, the described workflows don't cover that. What if I want to have my branch available from the upstream? (Release branches wil= l need that, right?) Finally, it looks like the TBDs near the end can be simply deleted now, as what's before covers that turf already. Thanks.