| commit | 75bf84270d750db4e32ed650e49afe7e6c078f7b | [log] [tgz] |
|---|---|---|
| author | Chris McDonald <cjmcdonald@chromium.org> | Wed Oct 28 17:32:12 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Oct 28 17:58:40 2020 |
| tree | d45289cc74c297404558a701e59e872ff439cbb2 | |
| parent | f385eb1fb070f096c28ef1388200d69d03627098 [diff] |
ebuild_faq: Add virtual version policy for chromeos-overlay Previously this overlay did not have an entry and people seem to have been using `1.5` as a default version for virtuals in chromeos-overlay, but that conflicts with the version used by "project-" overlays. Add a new entry to reflect that virtuals in chromeos-overlay should override those in chromiumos-overlay but not anything else. BUG=None TEST=None Change-Id: I6e733d1a71cfa3fdf274e3fb93b0eac88d469f9d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/2506132 Tested-by: Chris McDonald <cjmcdonald@chromium.org> Auto-Submit: Chris McDonald <cjmcdonald@chromium.org> Reviewed-by: Stephane Belmon <sbelmon@google.com> Commit-Queue: Stephane Belmon <sbelmon@google.com>
This directory contains public Chromium OS project documentation that is automatically rendered by Gitiles. The docs are written in Gitiles-flavored Markdown.
See the Chromium documentation guidelines and Chromium documentation best practices.
Markdown documents must follow the style guide.
This repository is managed by the repo tool, so you can make changes to it using the same techniques that you'd use for any other repositories in the project.
See the Contributing guide for more details.
You can also make changes to this repository without using the repo tool. This comes in handy when you don't have a Chromium OS checkout:
git clone https://chromium.googlesource.com/chromiumos/docs cd docs curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x .git/hooks/commit-msg git checkout -b changes (make some changes) git commit -a git push origin HEAD:refs/for/master
The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.
You can preview your local changes using scripts/preview_docs which utilizes Gerrit sandbox branches:
scripts/preview_docs README.md
You can also use md_browser, which is entirely local and does not require refs/sandbox/ push permission, but has somewhat inaccurate rendering:
# at top of Chromium OS checkout ./src/chromium/src/tools/md_browser/md_browser.py -d docs
Then browse to e.g. http://localhost:8080/README.md.
To review someone else's changes, apply them locally first, or just click the gitiles link near the top of a Gerrit file diff page.