|author||Manoj Gupta <firstname.lastname@example.org>||Thu Jun 20 03:34:14 2019|
|committer||chrome-bot <email@example.com>||Sat Jun 22 01:57:18 2019|
fuzzing: Add details about supressing errors in source code. Add docs about suppressing fuzzer errors using source code changes which is preferred over blocklist files. BUG=chromium:973144 TEST=Rendering in gitles looks ok. Change-Id: Id75292b61402ae251e20b9f5d50ba4d474112c1c Reviewed-on: https://chromium-review.googlesource.com/1668679 Tested-by: Manoj Gupta <firstname.lastname@example.org> Commit-Ready: Manoj Gupta <email@example.com> Legacy-Commit-Queue: Commit Bot <firstname.lastname@example.org> Reviewed-by: Mike Frysinger <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 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.