@@ -93,10 +93,11 @@ approaches.
9393Elijah also replied to Linus' alternative patch by discussing
9494different approaches. And Junio agreed with the direction Elijah was
9595taking, though he had not as much time as he would have liked to think
96- this through at that time.
96+ this through at that time. Junio discussed Linus' alternative patch
97+ anyway with Linus, and noted that it could cause problems in the case
98+ of local dirty changes.
9799
98- Junio discussed Linus' alternative patch anyway with Linus and then
99- Lars Schneider chimed in by suggesting to add a cache to speed up
100+ Then Lars Schneider chimed in by suggesting to add a cache to speed up
100101builds. Ævar Arnfjörð Bjarmason then replied to Lars and they
101102discussed this idea but concluded that it wouldn't work.
102103
@@ -109,9 +110,12 @@ Phillip Wood replied to Lars by sending a Perl script he has been
109110using to save and restore mtimes to avoid rebuilds.
110111
111112Elijah resent
[ his patch series
] ( https://public-inbox.org/git/[email protected] / ) 112- a few days later, and though there were further fixes needed, it
113- appears that the patch series will be merged in the "next" branch
114- soon.
113+ a few days later, and after a few minor fixes, the patch series was
114+ merged to "next" on May 8. The commit message of the final patch of
115+ the series in particular documents the
116+ [ "long and blemished history"
] ( https://public-inbox.org/git/[email protected] / ) 117+ of the can-working-tree-updates-be-skipped check and how it has been
118+ fixed.
115119
116120## Developer Spotlight: Johannes Schindelin (alias Dscho)
117121
0 commit comments