commit | b582800caa426261b718a8cedd989a93e3fa6d1a | [log] [tgz] |
---|---|---|
author | Andrew Paseltiner <apaseltiner@chromium.org> | Fri Feb 18 17:08:12 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 18 17:08:12 2022 |
tree | 75b95805a348b2fcd4ef04716c5f97f34494ba03 | |
parent | 73d1a9a719b580bd3ae1a8320684b223c53caef3 [diff] |
Reuse operator<< for source result enum in attribution simulator As we already do for triggers. Change-Id: I6dd1f1ca632f611bcb62acaa4cab5b3418ec9f2f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3473291 Auto-Submit: Andrew Paseltiner <apaseltiner@chromium.org> Reviewed-by: Nan Lin <linnan@chromium.org> Commit-Queue: Nan Lin <linnan@chromium.org> Cr-Commit-Position: refs/heads/main@{#972995}
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.