Re: Optimizing writes to unchanged files during merges?

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 16, 2018, 22:34 UTC
Message-ID: <xmqqvacqwzju.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CA+P7+xoVcPV_mFS3WpUvCUR7N4SzJ5WBZqpGT3VVWdkPjh6Qww@mail.gmail.com>

Jacob Keller <jacob.keller@gmail.com> writes:

Show 8 quoted lines

> On Mon, Apr 16, 2018 at 10:43 AM, Jacob Keller <jacob.keller@gmail.com> wrote:
> ...
> I think a better solution for your problem would be to extend the
> build system you're using to avoid rebuilding when the contents
> haven't changed since last build (possibly by using hashes?). At the
> very least, I would not want this to be default, as it could possibly
> result in *no* build when there should be one, which is far more
> confusing to debug.

Yup.

Even though I take many optional features that I do not see need to support on the core side and I do not plan to use personally, as long as the implementation is cleanly separated to make it clear that those who do not use them won't negatively affected, I would not want to have this in a system I maintain and get blamed by those who get burned by it. Something like ccache, not a version control system, is meant to serve this audience.