Lines Matching refs:to
7 Often it is necessary to update your patch set before it is merged. Refer to the
8 `Gerrit Upload Patch Set documentation`_ on how to do so.
10 If you need to modify an existing patch set with multiple commits, refer to the
13 How long will my changes take to merge into ``integration``?
20 set and the impact of any delay. Feel free to add a comment to your patch set
21 to get an estimate of when it will be merged.
23 * The quality of the patch set. Patches are likely to be merged more quickly if
28 API is likely to receive much greater scrutiny than a local change to a
32 maintainers may not wait for external review comments to merge trivial
33 bug-fixes but may wait up to a week to merge major changes, or ones requiring
36 * How many other patch sets are waiting to be integrated and the risk of
44 How long will it take for my changes to go from ``integration`` to ``master``?
49 the delay will be less than 1 day. If the TF maintainers are trying to merge
50 several things over the course of a few days, it might take up to a week.
53 The worst case is if the TF maintainers are trying to make a release while also
57 after the release, and then ``master`` will be fast-forwarded to ``integration``
58 1-2 days later. This whole process could take up 4 weeks. Please refer to the
60 will inform the patch owner if this is going to happen.
62 It is OK to create a patch based on commits that are only available in
64 that the dependency commits will change (for example due to patch set rework or
72 but would be after the CI has been transitioned to `trustedfirmware.org`_.