| commit | 9908ae44de56c2a743d7800ab11f488b15df3a51 | [log] [tgz] |
|---|---|---|
| author | Avi Drissman <[email protected]> | Fri Sep 29 16:31:11 2023 |
| committer | Chromium LUCI CQ <[email protected]> | Fri Sep 29 16:31:11 2023 |
| tree | fabdc4915e58af7031e9618e9bdd75e712cee98b | |
| parent | c3f61ea5aec3d3a931d9c69808d9d7a72a5c1b0c [diff] [blame] |
Update docs to remove fsmonitor warning git fsmonitor is fixed, so remove the warning. Bug: 1475405 Change-Id: I1e29fa523256bb362560025419fd2a37c246a99a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4902271 Commit-Queue: Josip Sokcevic <[email protected]> Auto-Submit: Avi Drissman <[email protected]> Reviewed-by: Josip Sokcevic <[email protected]> Cr-Commit-Position: refs/heads/main@{#1203311}
diff --git a/docs/ios/build_instructions.md b/docs/ios/build_instructions.md index ac89e1e..65dc7d2 100644 --- a/docs/ios/build_instructions.md +++ b/docs/ios/build_instructions.md
@@ -499,7 +499,8 @@ You can significantly speed up git by using [fsmonitor.](https://github.blog/2022-06-29-improve-git-monorepo-performance-with-a-file-system-monitor/) You should enable fsmonitor in large repos, such as Chromium and v8. Enabling -it globally will launch many processes and probably isn't worthwhile. The +it globally will launch many processes and probably isn't worthwhile. Be sure +you have at least version 2.43 (fsmonitor on the Mac is broken before then). The command to enable fsmonitor in the current repo is: ```shell