Updating the 'v4l-utils' README.chromium to include Revision Adding Revision field based on 'Version'. ``` $ git remote -v # This redirects to the provided URL. origin http://git.linuxtv.org/v4l-utils.git (fetch) origin http://git.linuxtv.org/v4l-utils.git (push) $ git show-ref --tags v4l-utils-1.6.0 02f0dda860a8b7d16792c616bdeb5b02303c288f refs/tags/v4l-utils-1.6.0 ``` R=henryhsu@chromium.org, posciak@chromium.org Bug: chromium:350851535 Change-Id: I096a650dd142f42bd2672fb4d706dce5f9989dbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5683162 Reviewed-by: Joey Scarr <jsca@google.com> Reviewed-by: Jordan Brown <rop@google.com> Auto-Submit: Jordan Brown <rop@google.com> Commit-Queue: Jordan Brown <rop@google.com> Cr-Commit-Position: refs/heads/main@{#1382664}
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.