From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Lars Schneider <larsxschneider@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Elijah Newren <newren@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
mgorny@gentoo.org, Peter Backes <rtc@helen.plasma.xg8.de>,
winserver.support@winserver.com, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Optimizing writes to unchanged files during merges?
Date: Tue, 17 Apr 2018 07:34:45 +0900 [thread overview]
Message-ID: <xmqqvacqwzju.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CA+P7+xoVcPV_mFS3WpUvCUR7N4SzJ5WBZqpGT3VVWdkPjh6Qww@mail.gmail.com> (Jacob Keller's message of "Mon, 16 Apr 2018 10:45:29 -0700")
Jacob Keller <jacob.keller@gmail.com> writes:
> 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.
next prev parent reply other threads:[~2018-04-16 22:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:14 Optimizing writes to unchanged files during merges? Linus Torvalds
2018-04-12 21:46 ` Junio C Hamano
2018-04-12 23:17 ` Junio C Hamano
2018-04-12 23:35 ` Linus Torvalds
2018-04-12 23:41 ` Linus Torvalds
2018-04-12 23:55 ` Linus Torvalds
2018-04-13 0:01 ` Linus Torvalds
2018-04-13 7:02 ` Elijah Newren
2018-04-13 17:14 ` Linus Torvalds
2018-04-13 17:39 ` Stefan Beller
2018-04-13 17:53 ` Linus Torvalds
2018-04-13 20:04 ` Elijah Newren
2018-04-13 22:27 ` Junio C Hamano
2018-04-16 1:44 ` Junio C Hamano
2018-04-16 2:03 ` Linus Torvalds
2018-04-16 16:07 ` Lars Schneider
2018-04-16 17:04 ` Ævar Arnfjörð Bjarmason
2018-04-17 17:23 ` Lars Schneider
2018-04-16 17:43 ` Jacob Keller
2018-04-16 17:45 ` Jacob Keller
2018-04-16 22:34 ` Junio C Hamano [this message]
2018-04-17 17:27 ` Lars Schneider
2018-04-17 17:43 ` Jacob Keller
2018-04-16 17:47 ` Phillip Wood
2018-04-16 20:09 ` Stefan Haller
2018-04-16 22:55 ` Elijah Newren
2018-04-16 23:03 ` Elijah Newren
2018-04-12 23:18 ` Linus Torvalds
2018-04-13 0:01 ` Elijah Newren
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=xmqqvacqwzju.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=mgorny@gentoo.org \
--cc=newren@gmail.com \
--cc=rtc@helen.plasma.xg8.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=winserver.support@winserver.com \
/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).