Skip to content

Add a few details about optimizing writes to unchanged files#293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chriscool merged 1 commit into from
May 14, 2018
Merged

Add a few details about optimizing writes to unchanged files #293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions rev_news/drafts/edition-39.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -93,10 +93,11 @@ approaches.
Elijah also replied to Linus' alternative patch by discussing
different approaches. And Junio agreed with the direction Elijah was
taking, though he had not as much time as he would have liked to think
this through at that time.
this through at that time. Junio discussed Linus' alternative patch
anyway with Linus, and noted that it could cause problems in the case
of local dirty changes.

Junio discussed Linus' alternative patch anyway with Linus and then
Lars Schneider chimed in by suggesting to add a cache to speed up
Then Lars Schneider chimed in by suggesting to add a cache to speed up
builds. Ævar Arnfjörð Bjarmason then replied to Lars and they
discussed this idea but concluded that it wouldn't work.

Expand All@@ -109,9 +110,12 @@ Phillip Wood replied to Lars by sending a Perl script he has been
using to save and restore mtimes to avoid rebuilds.

Elijah resent [his patch series](https://public-inbox.org/git/[email protected]/)
a few days later, and though there were further fixes needed, it
appears that the patch series will be merged in the "next" branch
soon.
a few days later, and after a few minor fixes, the patch series was
merged to "next" on May 8. The commit message of the final patch of
the series in particular documents the
["long and blemished history"](https://public-inbox.org/git/[email protected]/)
of the can-working-tree-updates-be-skipped check and how it has been
fixed.

## Developer Spotlight: Johannes Schindelin (alias Dscho)

Expand Down