Updated CodeReview (markdown)

Francesc Campoy 2016-11-01 10:50:29 -07:00
parent 72ebc11b28
commit c7b68225bd

@ -21,9 +21,9 @@ Please do NOT reply code review via email, as the message [will not be relayed t
# Work in progress
If you have changes that aren't ready to be reviewed, you can put a giant `"DO NOT REVIEW"` as the second line of the CL description, so that people who see it know not to look any further. Don't make it the first line, since then it will become the subject for the entire review, even after you've changed the description.
If you have changes that aren't ready to be reviewed, you can put a giant **`DO NOT REVIEW`** as the second line of the CL description, so that people who see it know not to look any further. Don't make it the first line, since then it will become the subject for the entire review, even after you've changed the description.
Similarly, if you would like to ensure that your changes are not merged by mistake, you can put a giant `"DO NOT SUBMIT"` as the second line of the CL description.
Similarly, if you would like to ensure that your changes are not merged by mistake, you can put **`DO NOT SUBMIT`** as the second line of the CL description.
If you don't need Gerrit's features, but just want to backup your work, share work between multiple clients, or have a staging UI to examine your changes, you can use a regular git remote.