From: "Óscar Fuentes" <oscarfv@telefonica.net>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Listing branches with bzr
Date: Wed, 02 Dec 2009 03:44:18 +0100 [thread overview]
Message-ID: <87my225c3h.fsf@telefonica.net> (raw)
In-Reply-To: <e01d8a50912011817g40381a67g54f1d3ea815bc96f@mail.gmail.com> (Lennart Borgman's message of "Wed, 2 Dec 2009 03:17:59 +0100")
Lennart Borgman <lennart.borgman@gmail.com> writes:
>>>> bzr branches http://bzr.savannah.gnu.org/r/emacs/
>>>
>>> Is that a bug, or?
>>
>> Not a bug AFAIK, just slow. For me it takes about 5 minutes.
>
>
> Isn't it doing the same work as on the server? Is it the network
> traffic that makes it so incredibly slow?
Possibly the operation is very chatty.
> I am thinking about Stephens reply (which I have not had time to
> respond to). He mentioned that git uses SHA to identify files why bzr
> does not do that? Is that the cause of the time trouble we are seeing?
I don't think so.
> I would consider that just as serious as a bug. But maybe there is
> something I do not understand there.
The `branches' command is implemented by the bzrtools plugin, so it
can't be considered a bug, or even a perfomance issue, on Bazaar proper.
Bazaar has a plugin architecture which makes very easy to add
functionality to it (in Python). There are some impressive plugins, like
my favorite, bzr-svn, which IMO turns bzr into a better Subversion
client than svn itself.
--
Óscar
next prev parent reply other threads:[~2009-12-02 2:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 19:06 Listing branches with bzr Eli Zaretskii
2009-12-01 21:46 ` Karl Fogel
2009-12-01 21:57 ` Xavier Maillard
2009-12-01 22:20 ` Jason Earl
2009-12-02 1:57 ` Lennart Borgman
2009-12-02 2:13 ` Óscar Fuentes
2009-12-02 2:17 ` Lennart Borgman
2009-12-02 2:44 ` Óscar Fuentes [this message]
2009-12-02 3:53 ` Stephen J. Turnbull
2009-12-02 6:21 ` Eli Zaretskii
2009-12-02 13:45 ` Martin Albisetti
2009-12-01 21:55 ` Stefan Monnier
2009-12-01 22:00 ` Dan Nicolaescu
2009-12-02 4:19 ` Eli Zaretskii
2009-12-02 23:24 ` Xavier Maillard
2009-12-03 3:55 ` Eli Zaretskii
2009-12-01 22:08 ` Alexander Belchenko
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=87my225c3h.fsf@telefonica.net \
--to=oscarfv@telefonica.net \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--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).