|author||Allen Webb <firstname.lastname@example.org>||Thu Mar 07 18:47:50 2019|
|committer||chrome-bot <email@example.com>||Thu Mar 07 23:04:13 2019|
selinux: Migrate /var/empty to /mnt/empty. This helps avoid races during chromeos_startup and eliminates the need for /var/empty to be set immutable. BUG=chromium:933582 Change-Id: I1a540fe268ec2f49195e235a169cc3a4000301d3 Reviewed-on: https://chromium-review.googlesource.com/1508985 Commit-Ready: Allen Webb <firstname.lastname@example.org> Tested-by: Allen Webb <email@example.com> Reviewed-by: Mike Frysinger <firstname.lastname@example.org>
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 curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x .git/hooks/commit-msg cd docs 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:
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.