chromium/src
0
Fork 0
Code Activity

avoid markdown tofu

Browse Source 
The markdown renderer used here fails to handle this non-ascii character:
3224cfecf5/docs/new_port_policy.md

TBR=jam@chromium.org

Change-Id: I82511db8e377488d87be767fe0b15dbcacb7e04e
Reviewed-on: https://chromium-review.googlesource.com/779124
Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com>
Reviewed-by: Mostyn Bramley-Moore <mostynb@vewd.com>
Cr-Commit-Position: refs/heads/master@{#517892}
This commit is contained in:
Mostyn Bramley-Moore
2017-11-20 19:55:39 +00:00
committed by Commit Bot
parent 9d40e79072
commit 0731f15c6f
1 changed files with 2 additions and 2 deletions

4
docs/new_port_policy.md

@ -8,5 +8,5 @@ Since every new port for Chromium has a maintenance cost, here are some guidelin
* These will not have bots on Google-run waterfalls (even FYI).
* Chromium engineers are not expected to maintain them.
* As much as possible, try to use existing branches/ifdefs.
* While changes in src/base are unavoidable, higher level directories shouldn’t have to change. i.e. existing porting APIs should be used. We would not accept new rendering pipelines as an example.
* Send an email to [src/OWNERS](https://chromium.googlesource.com/chromium/src/+/master/ENG_REVIEW_OWNERS) for approval.
* While changes in src/base are unavoidable, higher level directories shouldn't have to change. i.e. existing porting APIs should be used. We would not accept new rendering pipelines as an example.
* Send an email to [src/OWNERS](https://chromium.googlesource.com/chromium/src/+/master/ENG_REVIEW_OWNERS) for approval.