2154274a2a
This change removes references to git versions since Chromium developers should be using git from depot_tools, and since it isn't completely clear whether 2.39 is greater or lower than 2.8. This change also makes it clear that fsmonitor should be enabled on a per-repo basis rather than globally, for the best cost/benefit ratio. This change was inspired by the realization that enabling fsmonitor globally on Windows caused 179 fsmonitor process to be spawned when "gclient sync" was run. These processes commit an average of 86 MB on Windows leading to 15 GB of commit (only a few hundred MB of physical memory is used, but the commit usage is large enough to matter). Change-Id: I21c042462022088e11883bbf827276ee585fdaf3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4622567 Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1159338}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.