From: Rutger Nijlunsing <rutger@nospam.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Geert Bosch <bosch@adacore.com>,
Rene Scharfe <rene.scharfe@lsrfire.ath.cx>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <junkio@cox.net>
Subject: Re: RFC: New diff-delta.c implementation
Date: Mon, 24 Apr 2006 21:21:33 +0200 [thread overview]
Message-ID: <20060424192133.GA6446@nospam.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604241123490.18520@localhost.localdomain>
On Mon, Apr 24, 2006 at 11:57:38AM -0400, Nicolas Pitre wrote:
> On Mon, 24 Apr 2006, Geert Bosch wrote:
> >
> > The comparison is a bit between a O(n^2) sort that is fast on small
> > or mostly sorted inputs (but horrible on large ones) and a more
> > complex O(nlogn) algorithm that is a bit slower for the simple
> > cases, but far faster for more complex cases.
>
> Indeed. And since the primary goal for GIT is to manage relatively
> small files with relatively few differences then we have to optimize for
> that case while trying to simply limit the dammage in the other cases.
Like others (the large-Maildir-storage thread comes to mind), I am
looking into storing more diverse data (say, $HOME) into git repo's
and I would mind the O(n log n) instead of O(n^2) where the constant
factor of the first is larger than the constant factor of the second.
...but then again, I'm just a user ;)
--
Rutger Nijlunsing ---------------------------------- eludias ed dse.nl
never attribute to a conspiracy which can be explained by incompetence
----------------------------------------------------------------------
next prev parent reply other threads:[~2006-04-24 19:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 21:16 RFC: New diff-delta.c implementation Geert Bosch
2006-04-22 3:19 ` Nicolas Pitre
2006-04-22 11:04 ` Geert Bosch
2006-04-22 11:13 ` Junio C Hamano
2006-04-22 12:35 ` Geert Bosch
2006-04-22 12:51 ` Nicolas Pitre
2006-04-22 13:39 ` Geert Bosch
2006-04-22 17:03 ` Junio C Hamano
2006-04-22 17:28 ` Geert Bosch
2006-04-22 17:57 ` Junio C Hamano
2006-04-22 12:45 ` Nicolas Pitre
2006-04-22 14:17 ` Geert Bosch
2006-04-22 17:29 ` Junio C Hamano
2006-04-22 19:58 ` Nicolas Pitre
2006-04-22 5:21 ` Davide Libenzi
2006-04-22 9:12 ` Geert Bosch
2006-04-22 12:36 ` Rene Scharfe
2006-04-24 2:57 ` Geert Bosch
2006-04-24 5:27 ` Nicolas Pitre
2006-04-24 15:19 ` Geert Bosch
2006-04-24 15:57 ` Nicolas Pitre
2006-04-24 16:31 ` Geert Bosch
2006-04-24 18:24 ` Geert Bosch
2006-04-24 18:27 ` Geert Bosch
2006-04-24 19:21 ` Rutger Nijlunsing [this message]
2006-04-24 20:37 ` Petr Baudis
2006-04-24 18:44 ` Geert Bosch
2006-04-25 18:22 ` Rene Scharfe
2006-04-22 20:36 ` Davide Libenzi
2006-04-23 2:31 ` Geert Bosch
2006-04-24 19:10 ` Davide Libenzi
2006-04-24 19:23 ` Geert Bosch
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=20060424192133.GA6446@nospam.com \
--to=rutger@nospam.com \
--cc=bosch@adacore.com \
--cc=git@vger.kernel.org \
--cc=git@wingding.demon.nl \
--cc=junkio@cox.net \
--cc=nico@cam.org \
--cc=rene.scharfe@lsrfire.ath.cx \
/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.