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: bazaar: "unable to obtain lock" Date: Mon, 04 Jan 2010 02:05:48 -0500 Message-ID: References: <87my11gmf4.fsf@red-bean.com> <87fx6sqbnt.fsf@blah.blah> <877hs4m1dh.fsf@telefonica.net> <87fx6m7r18.fsf@blah.blah> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1262588927 16582 80.91.229.12 (4 Jan 2010 07:08:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2010 07:08:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kevin Ryde Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 08:08:40 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.50) id 1NRh3P-0003B1-Nm for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2010 08:08:40 +0100 Original-Received: from localhost ([127.0.0.1]:52746 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRh3P-0000ny-Rq for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2010 02:08:40 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRh17-0008Df-MC for emacs-devel@gnu.org; Mon, 04 Jan 2010 02:06:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRh11-0008A7-Cc for emacs-devel@gnu.org; Mon, 04 Jan 2010 02:06:15 -0500 Original-Received: from [199.232.76.173] (port=39688 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRh10-00089p-Un for emacs-devel@gnu.org; Mon, 04 Jan 2010 02:06:11 -0500 Original-Received: from [140.186.70.10] (port=51430 helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NRh10-0000ZN-Ke for emacs-devel@gnu.org; Mon, 04 Jan 2010 02:06:10 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1NRh0e-0002kF-IR; Mon, 04 Jan 2010 02:05:48 -0500 In-reply-to: <87fx6m7r18.fsf@blah.blah> (message from Kevin Ryde on Mon, 04 Jan 2010 09:38:27 +1100) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:119343 Archived-At: > From: Kevin Ryde > Date: Mon, 04 Jan 2010 09:38:27 +1100 > > Óscar Fuentes writes: > > > > A simple update after a few days can easily require to transfer 10 MB. > > Ah, thanks, that'd be very borderline. If it's potentially every commit > then it's a killer. I wonder if the wiki could put the requirements up > front a bit more. Without being too provocative something like > > The repo is about 300Mb. An initial checkout will download it in > full and may use about 1Gb of RAM while doing so. Subsequent > commits and updates could transfer as much as 10Mb even for modest > changes. But the last sentence could be blatantly misleading, it seems. For example, today's "bzr up" crams 185MB(!) of data through the wire. And that's only according to the progress indicator; who knows what else is going on on the protocol level? My previous update was 16 hours ago, and the files actually changed on the trunk since then are just a few: M lisp/ChangeLog M lisp/vc-bzr.el M src/ChangeLog M src/dbusbind.c It sounds like such a massive update is due to the change in the branches configuration in the repository: most of the branches were moved to the old-branches and other-branches ``subdirectories''. Maybe this is a very infrequent situation, but it does show the potential. So I'm not sure if we should tell anything about traffic beyond the initial branch, whose size is more or less known and changes very slowly.