From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: "Bzr for Emacs Devs" including upstream branches
Date: Mon, 12 Apr 2010 20:28:39 +0200 [thread overview]
Message-ID: <87y6gsa5k8.fsf@telefonica.net> (raw)
In-Reply-To: 83tyrgy2z4.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> After some hunting around I tried:
>>
>> bzr branches sftp://arobert@bzr.savannah.gnu.org/srv/bzr/emacs/
>>
>> but this just started downloading something at 1K / second and never
>> got anywhere.
>
> Just be patient. It takes a lot of time with a remote repository, but
> eventually you will get a list.
Last time I tried, long time ago, it required more than 5 minutes over
http. IIRC it does a lot of round trips so the nearer you are from the
server (on Internet distance) the faster it will work.
> And since new branches aren't added too frequently, this is a rarely
> used command, so its slowness is not too much of an annoyance.
Precisely, one of the reasons for using `bzr branches' is to check the
presence of new branches :-)
`bzr branches' is just a hack implemented on a plugin as a "best effort"
and it is quite expensive due to the limitations of using bzrlib (which
was not designed with that use on mind) over a dumb remote file access
protocol (sftp or, worse, http). It does not work with the smart server,
IIRC.
prev parent reply other threads:[~2010-04-12 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 17:01 "Bzr for Emacs Devs" including upstream branches Adrian Robert
2010-04-12 17:16 ` Chong Yidong
2010-04-12 17:58 ` Adrian Robert
2010-04-12 18:20 ` Glenn Morris
2010-04-12 19:01 ` Adrian Robert
2010-04-12 17:50 ` Eli Zaretskii
2010-04-12 18:28 ` Óscar Fuentes [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y6gsa5k8.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.