Lines Matching full:change
32 If you are willing to change Skia codebase, it's nice to add a test at the same
39 Unit tests are best, but if your change touches rendering and you can't think of
41 of SampleApp. Also, if your change is the GPU code, you may not be able to write
56 Now that you've made a change and written a test for it, it's ready for the code
81 Use git cl to upload your change:
98 by me**. Select the change you want to submit for review and click **Edit
101 change off for review. Unless you publish your change, no one will know to look
106 send the email directly when uploading a change in both gcl and git-cl.
127 change. Be sure to respond to all comments before you request review of an
149 Once your commit has gone in, you should delete the branch containing your change:
160 Skia's principal downstream user is Chromium, and any change to Skia rendering
161 output can break Chromium. If your change alters rendering in any way, you are
176 [How to land Skia changes that change Blink layout test results](../chrome/layouttest)
178 If you're changing the Skia API, you may need to make an associated change in Chromium.
188 commit your change directly to Skia's repository.
207 git-cl will squash all your commits into a single one with the description you used when you uploaded your change.
