From: Nico Williams <nico@cryptonector.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
git discussion list <git@vger.kernel.org>
Subject: Re: Our merge bases sometimes suck
Date: Fri, 20 Jun 2014 16:17:37 -0500 [thread overview]
Message-ID: <CAK3OfOjfyrsN47Ho0MFh4VZUg6YMjjwPOa16iuw3xtqyhz16hg@mail.gmail.com> (raw)
In-Reply-To: <xmqqtx7gdqbt.fsf@gitster.dls.corp.google.com>
On Fri, Jun 20, 2014 at 1:53 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Michael Haggerty <mhagger@alum.mit.edu> writes:
>> [...]
>
> Hmph, but that obviously will become very expensive to compute as
> project grows.
That's the main reason to like Fossil's approach (namely, the use of
SQL, specifically SQLite3): you can write declarative queries and let
the query planner optimize.
(That's also about the only thing I like about Fossil: the use of
SQL/SQLite3, and all that that implies. Fossil is otherwise an
anti-git, and that makes it useless for me.)
Pardon the intrusion,
Nico
--
next prev parent reply other threads:[~2014-06-20 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 22:12 Our merge bases sometimes suck Michael Haggerty
2014-06-13 9:38 ` Michael J Gruber
2014-06-13 10:13 ` Michael Haggerty
2014-06-13 15:52 ` Jakub Narębski
2014-06-13 22:14 ` Michael Haggerty
2014-06-13 22:35 ` Junio C Hamano
2014-06-17 15:08 ` Junio C Hamano
2014-06-17 15:44 ` Michael Haggerty
2014-06-20 6:53 ` Junio C Hamano
2014-06-20 8:53 ` Michael Haggerty
2014-06-20 21:17 ` Nico Williams [this message]
2014-06-23 11:43 ` Jakub Narębski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK3OfOjfyrsN47Ho0MFh4VZUg6YMjjwPOa16iuw3xtqyhz16hg@mail.gmail.com \
--to=nico@cryptonector.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
/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 public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).