From: Stefan Beller <sbeller@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Elijah Newren <newren@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Optimizing writes to unchanged files during merges?
Date: Fri, 13 Apr 2018 10:39:03 -0700 [thread overview]
Message-ID: <CAGZ79kbs0heVvqMf2cjBtxtYs48CFFaM+9+YzB6gUwzWScvr=A@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwi9pTAJT_qtv=vHLgu=B1fdXBoD96i8Y5xnbS=zrfSzg@mail.gmail.com>
Hi Linus,
On Fri, Apr 13, 2018 at 10:14 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Comments? Because considering the problems this code has had, maybe
> "stupid" really is the right approach...
Would s/read/xread/ make sense in working_tree_matches ?
If read returns unexpectedly due to EINTR or EAGAIN,
this is no correctness issue, but you'd have to recompile the kernel.
Stefan
next prev parent reply other threads:[~2018-04-13 17:39 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 [this message]
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
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='CAGZ79kbs0heVvqMf2cjBtxtYs48CFFaM+9+YzB6gUwzWScvr=A@mail.gmail.com' \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).