|author||Jorge Lucangeli Obes <email@example.com>||Fri Apr 09 14:51:21 2021|
|committer||Commit Bot <firstname.lastname@example.org>||Fri Apr 09 15:02:09 2021|
sandboxing: Remove uses of sl*ve, replace with MS_SL*VE. This is not great, but the upstream kernel terminology will take longer to change, and at least now it's clear it's a flag name. BUG=chromium:1183781 TEST=None Change-Id: I83cf4668ff353e0322d6601771eb14a60b6d73cc Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/2818338 Tested-by: Jorge Lucangeli Obes <email@example.com> Auto-Submit: Jorge Lucangeli Obes <firstname.lastname@example.org> Reviewed-by: Allen Webb <email@example.com> Commit-Queue: Allen Webb <firstname.lastname@example.org> Commit-Queue: Jorge Lucangeli Obes <email@example.com>
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:
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.