help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How expansive "bzr update" for Emacs trunk?


From: Jason Earl
Subject: Re: How expansive "bzr update" for Emacs trunk?
Date: Wed, 08 Dec 2010 15:21:19 -0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

On Mon, Jul 26 2010, Oleksandr Gavenko wrote:

>   $ cat ~/devel/emacs/trunk/.bzr/branch/branch.conf
> parent_location = http://bzr.savannah.gnu.org/r/emacs/trunk/
> submit_branch = http://bzr.savannah.gnu.org/r/emacs/trunk/
> bound_location = http://bzr.savannah.gnu.org/r/emacs/trunk/
> bound = True
>
> I mark that "bzr update" take about 1 MiB for
> "Finding Revisions" and a lot MiB
> (5.5 MiB between yesterday and today).
>
> Is really bzr so dumb that require a lot of network traffic?
> Or into Emacs sources go a lot of commit?
>
> I restricted with 3G or GPRS Internet connection.
> One time a month commit I get about 5 hours
> (~7 KiB/sec download speed)!
>
> Is bzr use plain (uncompressed) schema for
> propagating changes?
>
> So may be good switch to ssh protocol and set compression?
>
> I also heir (but sorry if not correct) that bzr
> developed for local network connection.
> And for example if exist new changes it send
> last 50 changeset even new only 1!

A partial solution, if you don't need to commit is to use launchpad's
mirror of the Emacs repository.  To get the bzr+ssh access (that allows
you to use the smart server) you'll have to actually have a launchpad
account (and I think you need to upload a public ssh key), but it is a
pretty big improvement over the dumb bzr server that is available from
savannah.

If signing up for launchpad.net is problematic then email me privately
(the email address will work) and I will send you a link to a bzr mirror
of the repository that I maintain that uses the straight bzr:// protocol
and doesn't require any authentication.

Alternatively there is a git mirror at:

http://repo.or.cz/w/emacs.git

I hope this is helpful.

Jason


reply via email to

[Prev in Thread] Current Thread [Next in Thread]