From: Werner LEMBERG <wl@gnu.org>
To: ofv@wanadoo.es
Cc: emacs-devel@gnu.org
Subject: Re: `bzr viz' slooow
Date: Wed, 27 Jan 2010 12:30:24 +0100 (CET) [thread overview]
Message-ID: <20100127.123024.170021878.wl@gnu.org> (raw)
In-Reply-To: <87pr4vvm4g.fsf@telefonica.net>
>> Maybe. However, it is quite generic and basically independent of
>> the version of bzr. In other words, it uses calls to the bzr
>> infrastructure to get the data.
>
> And why do you think that it is bzr the main culprit? Haven't you
> seen the timings about qlog, which does the same thing but much
> faster?
I'll try qlog.
> Have you forgotten about the possibility of displaying the graph at
> the same time that the data is collected, the same way gitk does?
I've suggested exactly that on the bzr-gtk mailing list meanwhile.
> Or is this about blaming bzr and make it look bad?
Not at all. However, gtk and not qt is the primary graphical
environment recommended for GNU projects, right? From a political
point of view, bzr-gtk should thus be the preferred tool...
>> Either your machine is much faster than mine, or you have `light'
>> checkout.
>
> Actually, building the graph on a lightweight checkout of a remote
> branch will require *much* more time.
OK.
Werner
next prev parent reply other threads:[~2010-01-27 11:30 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
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 [this message]
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=20100127.123024.170021878.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).