Lines Matching refs:change

11 This tutorial will guide you through the process of making a change to
13 change to Clang, but the steps for other parts of LLVM are the same.
14 Even though the change we'll be making is simple, we're going to cover
31 The change we're making
160    lldb".In this example, we'll be making a change to Clang, so we
237 To verify our change, we can build clang and manually check that it
282 iterate on a change! Instead, let's find a way to re-run just the
309 We'll save the change to a local git branch. This lets us work on other
310 things while the change is being reviewed. Changes should have a
312 the change was made.
319 Now we're ready to send this change out into the world! By the way,
336 well. The author of a change will often assign a specific reviewer (git
339 As our change is fairly simple, we'll add the cfe-commits mailing list
346 Uploading a change for review
354 Now you can upload your change for review:
360 This creates a review for your change, comparing your current commit
371 When you upload a change for review, an email is sent to you, the
382 The reviewer can leave comments on the change, and you can reply. Some
390 Updating your change
399 again to update the change and notify the reviewer. Typically this is a
406 When the reviewer is happy with the change, they will **Accept** the
415 As this is your first change, you won't have access to commit it
420    patch for me? Please use "My Name my@email" to commit the change.
422 The review will be updated when the change is committed.
485 Let's say you have a change on a local git branch, reviewed and ready to
517 You should see your change `on
525 Once your change is submitted it will be picked up by automated build
535 want to follow along how your change is affecting the build bots, **this
540 continuously broken; if your change broke the build, you will see a red
543 change might introduce a hidden new failure.