From: Bruce Stephens <bruce.stephens@isode.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
newsgroups@catchall.shelter13.net, git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Mon, 28 Sep 2009 12:17:15 +0100 [thread overview]
Message-ID: <804oqn5nes.fsf@tiny.isode.net> (raw)
In-Reply-To: <94a0d4530909280401q4a451697re8954320682662f2@mail.gmail.com> (Felipe Contreras's message of "Mon, 28 Sep 2009 14:01:48 +0300")
Felipe Contreras <felipe.contreras@gmail.com> writes:
[...]
> Ok, thanks for pointing that out. I was thinking that maybe 'git
> blame' would also be slightly faster on hg, but I really don't know.
hg (and git) store binary deltas. AFAIK neither attempts to use those
to produce output for blame, diff, etc. (git's deltas may well be
slightly different from mercurial's, in that git's can be deltas with
respect to something arbitrary so even if they had a suitable line-based
format they'd be useless for diff, blame.)
Similarly for the other major systems, with the exception of (I think)
bzr and darcs. (I don't know how bzr or darcs actually work, but IIRC
they both have line-based storage that in principle might be usable in
computing blame and diff.)
[...]
next prev parent reply other threads:[~2009-09-28 11:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 12:24 Deciding between Git/Mercurial Anteru
2009-09-27 18:01 ` Robin Rosenberg
2009-09-27 18:10 ` Anteru
2009-09-27 18:44 ` Alex Riesen
2009-09-27 18:51 ` Mark Struberg
2009-09-27 19:18 ` Anteru
2009-09-27 19:31 ` Alex Riesen
2009-09-27 19:34 ` Erik Faye-Lund
2009-09-27 18:55 ` Pascal Obry
2009-10-22 8:01 ` Martin Langhoff
2009-09-28 8:36 ` Felipe Contreras
2009-09-28 8:42 ` Matthieu Moy
2009-09-28 10:08 ` Johannes Schindelin
2009-09-28 11:01 ` Felipe Contreras
2009-09-28 11:17 ` Bruce Stephens [this message]
2009-09-30 11:14 ` Matthias Andree
2009-09-28 11:32 ` Dilip M
2009-09-28 20:54 ` Damien Wyart
2009-09-28 21:09 ` Steven Noonan
2009-09-28 21:33 ` Sverre Rabbelier
2009-09-28 23:56 ` Randal L. Schwartz
2009-09-29 0:01 ` Sverre Rabbelier
2009-09-29 7:44 ` Mike Ralphson
2009-09-29 8:21 ` Matthieu Moy
2009-09-29 8:22 ` Sverre Rabbelier
2009-09-28 23:11 ` Jakub Narebski
2009-09-29 0:32 ` Jakub Narebski
2009-09-29 6:32 ` Anteru
2009-09-29 18:44 ` Leo Razoumov
2009-09-29 18:58 ` Jakub Narebski
2009-09-29 19:55 ` Matthieu Moy
2009-09-30 0:49 ` Leo Razoumov
2009-09-30 6:28 ` Björn Steinbrink
2009-09-30 9:17 ` Andreas Ericsson
2009-09-30 11:09 ` Jakub Narebski
2009-09-29 1:55 ` Paolo Bonzini
2009-09-29 8:44 ` Daniele Segato
2009-09-29 8:54 ` Dilip M
2009-09-30 11:09 ` Matthias Andree
2009-09-30 22:05 ` Daniel Barkalow
2009-10-22 2:38 ` Dilip M
2009-10-22 6:50 ` Anteru
2009-10-22 7:12 ` Dilip M
2009-10-22 7:35 ` Anteru
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=804oqn5nes.fsf@tiny.isode.net \
--to=bruce.stephens@isode.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=newsgroups@catchall.shelter13.net \
/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.
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.