Revert "[Docs] Add wiki content to Markdown docs"
This reverts commit 7ed2476eea2c2a50fd40ec3e711dcb311d472753. This was supposed to be committed to the linux-syscall-support project. The two CLs landing at the sametime confused me. Note: LSS has been updated via commit 08056836f2b4a5747daff75435d10d6. Review URL: https://codereview.chromium.org/1395743002 .
This commit is contained in:
parent
4ee6f3cd1c
commit
a31f601d90
2 changed files with 0 additions and 31 deletions
|
@ -1,26 +0,0 @@
|
|||
# How to get an LSS change committed
|
||||
|
||||
## Review
|
||||
|
||||
You get your change reviewed, you can upload it to
|
||||
http://codereview.chromium.org (Rietveld) using `git cl upload` from Chromium's
|
||||
`depot-tools`.
|
||||
|
||||
## Testing
|
||||
|
||||
Unfortunately, LSS has no automated test suite.
|
||||
|
||||
You can test LSS by patching it into Chromium, building Chromium, and running
|
||||
Chromium's tests. (See [ProjectsUsingLSS](projects_using_lss.md).)
|
||||
|
||||
You can compile-test LSS by running:
|
||||
|
||||
gcc -Wall -Wextra -Wstrict-prototypes -c linux_syscall_support.h
|
||||
|
||||
## Rolling into Chromium
|
||||
|
||||
If you commit a change to LSS, please also commit a Chromium change to update
|
||||
`lss_revision` in Chromium's DEPS file.
|
||||
|
||||
This ensures that the LSS change gets tested, so that people who commit later
|
||||
LSS changes don't run into problems with updating `lss_revision`.
|
|
@ -1,5 +0,0 @@
|
|||
# Projects that use linux\_syscall\_support.h
|
||||
|
||||
* Chromium
|
||||
* Breakpad (built as part of Chromium)
|
||||
* Native Client, in nacl\_bootstrap.c (also built as part of Chromium)
|
Loading…
Reference in a new issue