From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Is bzr+ssh's speed satisfactory?
Date: Sat, 16 Oct 2010 09:52:37 +0200 [thread overview]
Message-ID: <83fww6bmm2.fsf@gnu.org> (raw)
In-Reply-To: <20101016.080817.485378771.wl@gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2004, Size: 920 bytes --]
> Date: Sat, 16 Oct 2010 08:08:17 +0200 (CEST)
> From: Werner LEMBERG <wl@gnu.org>
> Cc: emacs-devel@gnu.org
>
> However, the amount of data transferred
> by bzr is still excessively large. For example, updating from
> rev. 101894 (Oct. 10th) to today's rev. 101979 (with `bzr pull') used
> more than 20MByte! Looking at the amount of changes actually applied
> to the repository, I estimate that git would need only approx. 200 to
> 300kByte ^[$(Q#|^[(B this is 70 to 100 times less...
>
> It would be great if someone using an emacs git repository could
> verify my estimation.
>
> git compresses the data on the remote side before transferring it.
> Does bzr omit that step? Maybe I'm missing a bzr option? Otherwise,
> it looks like a severe flaw in the design.
These questions are better sent to the Bazaar list
(bazaar@lists.canonical.com), where the Bazaar developers can give
definitive answers to them.
next prev parent reply other threads:[~2010-10-16 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 4:59 (no subject) Richard Stallman
2010-10-16 6:08 ` Werner LEMBERG
2010-10-16 6:10 ` Werner LEMBERG
2010-10-16 7:54 ` Is bzr+ssh's speed satisfactory? Eli Zaretskii
2010-10-16 7:52 ` Eli Zaretskii [this message]
2010-10-18 6:26 ` (no subject) Richard Stallman
2010-10-16 7:49 ` Is bzr+ssh's speed satisfactory? Eli Zaretskii
2010-10-19 18:28 ` (no subject) Glenn Morris
2010-10-19 18:43 ` bzr on Savannah Glenn Morris
2010-10-19 18:58 ` Eli Zaretskii
2010-10-19 19:03 ` Glenn Morris
2010-10-24 3:54 ` Richard Stallman
2010-10-24 19:50 ` Glenn Morris
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=83fww6bmm2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=wl@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.