From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Matthieu Moy Newsgroups: gmane.comp.version-control.bazaar-ng.general,gmane.emacs.devel Subject: Re: Emacs Bazaar repository Date: Fri, 14 Mar 2008 10:58:13 +0100 Message-ID: References: <87skyvse7k.fsf@xmission.com> <86ejae96t4.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1205488772 23000 80.91.229.12 (14 Mar 2008 09:59:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Mar 2008 09:59:32 +0000 (UTC) Cc: Andreas Schwab , emacs-devel@gnu.org, bazaar@lists.canonical.com To: David Kastrup Original-X-From: bazaar-bounces@lists.canonical.com Fri Mar 14 10:59:59 2008 Return-path: Envelope-to: gcvbg-bazaar-ng@m.gmane.org Original-Received: from chlorine.canonical.com ([91.189.94.204]) by lo.gmane.org with esmtp (Exim 4.50) id 1Ja6hc-0001ox-SS for gcvbg-bazaar-ng@m.gmane.org; Fri, 14 Mar 2008 10:59:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=chlorine.canonical.com) by chlorine.canonical.com with esmtp (Exim 4.60) (envelope-from ) id 1Ja6h1-00043Z-LL; Fri, 14 Mar 2008 09:59:15 +0000 Original-Received: from imag.imag.fr ([129.88.30.1]) by chlorine.canonical.com with esmtp (Exim 4.60) (envelope-from ) id 1Ja6gy-00043M-Ch for bazaar@lists.canonical.com; Fri, 14 Mar 2008 09:59:12 +0000 Original-Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.8/8.13.8) with ESMTP id m2E9wDrX016417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 14 Mar 2008 10:58:13 +0100 (CET) Original-Received: from bauges.imag.fr ([129.88.43.5]) by mail-veri.imag.fr with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1Ja6g1-0001CY-Bi; Fri, 14 Mar 2008 10:58:13 +0100 Original-Received: from moy by bauges.imag.fr with local (Exim 4.63) (envelope-from ) id 1Ja6g1-000183-9L; Fri, 14 Mar 2008 10:58:13 +0100 In-Reply-To: <86ejae96t4.fsf@lola.quinscape.zz> (David Kastrup's message of "Thu\, 13 Mar 2008 12\:55\:51 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (imag.imag.fr [129.88.30.1]); Fri, 14 Mar 2008 10:58:14 +0100 (CET) X-IMAG-MailScanner-Information: Please contact MI2S MIM for more information X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-SpamCheck: X-IMAG-MailScanner-From: moy@imag.fr X-BeenThere: bazaar@lists.canonical.com X-Mailman-Version: 2.1.8 Precedence: list List-Id: bazaar discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bazaar-bounces@lists.canonical.com Errors-To: bazaar-bounces@lists.canonical.com Xref: news.gmane.org gmane.comp.version-control.bazaar-ng.general:38536 gmane.emacs.devel:92502 Archived-At: David Kastrup writes: > Andreas Schwab writes: > >> My first impression is that bzr is slow, so slow that it is completely >> unusable. How can it come that a simple bzr log takes more than a >> minute to even start? Even cvs log is instantaneous in comparison, >> although it has to request the log from the server. > > I find this surprising: "git log" is pretty much instantaneous, and git > recalculates a code piece's history in the process (renaming and copying > is not tracked by git, but calculated on the fly when you ask for log > output). Actually the full "git log" can be long, but in practice, "git log" seems _always_ instantaneous, since: * git log pipes itself to less by default, so you get something stable in your terminal as soon as "git log" has outputed a few lines. * git log can show the output as it finds it. It can show the output for HEAD immediately, then the ancestors of HEAD, then the grandparents, ... As opposed to that, bzr has to get a global view of history at least to get the revision numbers (there was some plans caching this information, I don't know what's the status). That said, the time for bzr log to start should clearly not be _that_ long. I suspect it's done on a light checkout (therefore needing network access), which git can't do at all for example.