From: Werner LEMBERG <wl@gnu.org>
To: ofv@wanadoo.es
Cc: emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Tue, 26 Jan 2010 23:16:26 +0100 (CET) [thread overview]
Message-ID: <20100126.231626.78379055.wl@gnu.org> (raw)
In-Reply-To: <877hr4ww3c.fsf@telefonica.net>
> In any case I wouldn't expect to match the performance of git,
> though.
Well...
> BTW, "less than a minute" qualifies as an slow operation for
> me, so git slow,
BUT: gitk displays something useful (the most recent commits) after a
few seconds, and I can start to inspect the data; apparently a
background process collects the remaining commit entries. It takes
about a minute if you press the `End' button to see the very first
commit in the whole repository. On the other hand, `bzr viz' is
unusable for really five minutes.
> bzr is sloow (note just one extra `o')
In the light of my previous paragraph, I strongly disagree. bzr is
sloooow (note the four `o's); it takes 50 times more time until I can
actually do something.
Werner
next prev parent reply other threads:[~2010-01-26 22:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 17:05 `bzr viz' slooow Werner LEMBERG
2010-01-26 17:48 ` Eli Zaretskii
2010-01-26 22:07 ` Werner LEMBERG
2010-01-27 4:11 ` Eli Zaretskii
2010-01-27 6:14 ` Werner LEMBERG
2010-01-27 11:29 ` Eli Zaretskii
2010-01-27 12:01 ` Werner LEMBERG
2010-01-27 13:03 ` Eli Zaretskii
2010-01-26 18:37 ` Óscar Fuentes
2010-01-26 22:16 ` Werner LEMBERG [this message]
2010-01-26 23:13 ` Óscar Fuentes
2010-01-27 6:15 ` Werner LEMBERG
2010-01-26 22:59 ` Dan Nicolaescu
2010-01-27 5:22 ` Ken Hori
2010-01-27 6:02 ` Werner LEMBERG
2010-01-27 11:10 ` Óscar Fuentes
2010-01-27 11:30 ` Werner LEMBERG
2010-01-27 11:51 ` Werner LEMBERG
2010-01-27 12:05 ` Eli Zaretskii
2010-01-27 12:27 ` Óscar Fuentes
2010-01-27 13:02 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100126.231626.78379055.wl@gnu.org \
--to=wl@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).