commit | c47ef307012e218bdeb7ad6e65a0c0e1773bf885 | [log] [tgz] |
---|---|---|
author | Allen Webb <allenwebb@google.com> | Wed Oct 31 22:01:40 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Nov 01 00:52:53 2018 |
tree | d45a0e45b1b3f7153cb68d67074df84e7c29be2d | |
parent | 29ae16da4d97ff6a4d882b87584d9cf8a55545af [diff] |
fuzzing: Add clarification to binary path. This clarifies the absolute path where fuzzing targets are emerged. Change-Id: Idce1b536591575dbcb73a2bad9a23996795a165b Reviewed-on: https://chromium-review.googlesource.com/1311633 Commit-Ready: Allen Webb <allenwebb@google.com> Tested-by: Allen Webb <allenwebb@google.com> Reviewed-by: Caroline Tice <cmtice@chromium.org>
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.
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
:
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 ./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.