all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Werner LEMBERG <wl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bzr vs. git repository
Date: Sat, 01 Jan 2011 11:52:17 +0200	[thread overview]
Message-ID: <83zkrlosry.fsf@gnu.org> (raw)
In-Reply-To: <20110101.092838.211465745.wl@gnu.org>

> Date: Sat, 01 Jan 2011 09:28:38 +0100 (CET)
> From: Werner LEMBERG <wl@gnu.org>
> 
> As you can see, bzr still needs about three times more bandwidth in
> both receiving and sending...

So what?  In my testing, both on GNU/Linux and on MS-Windows,
update/pull times are very similar (with bzr slightly _faster_ on
GNU/Linux).  That includes the initial "bzr branch" vs "git clone" (10
min for bzr vs 15 for git).  Other common operations are mostly
comparable as well.  (A great surprise was "annotate", which, for
xdisp.c, took 1 minute with bzr, but a whopping 4.5 minutes with git.
But I see that as a curiosity.)

I don't think this will convince anyone to switch, but frankly, I no
longer understand what is all that fuss with git's speed.  Coupled
with the fact that the git repository seems to be updated only once in
a while, I see no good reasons to use git at all, at least not for
reasons of speed.



  reply	other threads:[~2011-01-01  9:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-01  8:28 bzr vs. git repository Werner LEMBERG
2011-01-01  9:52 ` Eli Zaretskii [this message]
2011-01-01  9:54   ` Werner LEMBERG
2011-01-01 10:12     ` Eli Zaretskii
2011-01-01 11:04       ` Werner LEMBERG
2011-01-01 12:36         ` Óscar Fuentes
2011-01-01 10:13     ` Frank Schmitt
2011-01-01 10:14   ` David Kastrup
2011-01-01 11:36     ` Eli Zaretskii
2011-01-01 11:44 ` Eli Zaretskii
2011-01-01 17:28 ` Stefan Monnier
2011-01-02  0:33 ` Richard Stallman

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=83zkrlosry.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.