Re: Our merge bases sometimes suck
- From
- Nico Williams <nico@cryptonector.com>
- Date
- Jun 20, 2014, 21:17 UTC
- Message-ID
- <CAK3OfOjfyrsN47Ho0MFh4VZUg6YMjjwPOa16iuw3xtqyhz16hg@mail.gmail.com>
- 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:
Show 5 quoted lines
> 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 --