| commit | c936f8b50e8ede6a714ae1f0d360fbb25752cdcf | [log] [tgz] |
|---|---|---|
| author | Andrii Shyshkalov <tandrii@chromium.org> | Tue Feb 21 10:58:12 2017 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 21 10:58:27 2017 |
| tree | 2749f9291d1dfc373ecf7139c33023e36a0b447f | |
| parent | 558e859bd582eea405b1a3fe2bf3db1e8529677d [diff] |
Revert "Make a better formatting." This reverts commit 558e859bd582eea405b1a3fe2bf3db1e8529677d. Reason for revert: <INSERT REASONING HERE> Original change's description: > Make a better formatting. > > BUG=N/A > > Change-Id: I246c0c6cf9506ef1873c81a0a0a56f2749f848a9 > Reviewed-on: https://chromium-review.googlesource.com/445238 > Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> > Reviewed-by: Alice ForReview <alice4review@gmail.com> > TBR=tandrii@chromium.org,alice4review@gmail.com NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=N/A Change-Id: I0f65983352ecaedd4d20b78aa3e2ed4e70cb9d4c Reviewed-on: https://chromium-review.googlesource.com/445299 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
First make sure you have proper codereview.settings like the one in this repo.
Committers set the CQ label to either 1 (Dry run) or 2 (Ready for CQ) which will automatically submit change after all conditions are met:
Clone it this normal way:
git clone https://chromium.googlesource.com/playground/gerrit-cq/normal
Initialize your repository first:
git new-branch feature # hack, hack, hack git add changed.file git commit # You can hack more, and commit again, # but they'll all be squashed by default in git cl upload step. # OK, now ask others for review: git cl upload # Make changes locally per review. git add changed.file git commit # Now upload new patchset. git cl upload
Does it work with numbers?