From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Locks on the Bzr repository Date: Thu, 19 Aug 2010 13:08:12 -0400 Message-ID: References: <4C6D57EE.70109@gnu.org> <4C6D606C.9010309@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1282237708 18745 80.91.229.12 (19 Aug 2010 17:08:28 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 19 Aug 2010 17:08:28 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 19 19:08:26 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.69) (envelope-from ) id 1Om8bG-0006Es-GT for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 19:08:22 +0200 Original-Received: from localhost ([127.0.0.1]:56414 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om8bF-000298-No for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 13:08:21 -0400 Original-Received: from [199.232.76.173] (port=52428 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om8b8-00028F-6S for emacs-devel@gnu.org; Thu, 19 Aug 2010 13:08:14 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Om8b7-0003xi-7I for emacs-devel@gnu.org; Thu, 19 Aug 2010 13:08:13 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:38452) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Om8b7-0003xd-1k for emacs-devel@gnu.org; Thu, 19 Aug 2010 13:08:13 -0400 Original-Received: from dann by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1Om8b7-00076F-0H; Thu, 19 Aug 2010 13:08:13 -0400 In-Reply-To: <4C6D606C.9010309@gnu.org> (Jason Rumney's message of "Fri\, 20 Aug 2010 00\:48\:44 +0800") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) 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:128883 Archived-At: Jason Rumney writes: > On 20/8/2010 12:43 AM, Dan Nicolaescu wrote: >> I have seen the lock problem happen when using -m<...> and on very >> well connected machine, so it's might be just bzr being bzr. > > When you say you've seen the problem, is it your own locks you are > seeing, or locks held by someone else? Normally you would only see My own locks. Sometimes commits fail (in a up to date tree!) after a long time, and then I have to remove my own locks to try again. And it's not even that seldom: $ grep -c break.lock .bzr.log* .bzr.log:3 .bzr.log.old:45