Lines Matching full:patch

22 <li><a href="#formatting">Patch formatting</a>
50 <h2 id="formatting">Patch formatting</h2>
65 <li>Subsequent patch comments should describe the change in more detail,
76 <li>If a patch addresses a bugzilla issue, that should be noted in the
77 patch comment.  For example:
81 <li>If a patch addresses a issue introduced with earlier commit, that should be
82 noted in the patch comment.  For example:
86 <li>If there have been several revisions to a patch during the review
103 <li>If someone tested your patch, document it with a line like this:
107 <li>If the patch was reviewed (usually the case) or acked by someone,
113 <li>If sending later revision of a patch, add all the tags - ack, r-b,
115 patch has already been reviewed.
116 <li>In order for your patch to reach the prospective reviewer easier/faster,
148 Whenever possible and applicable, test the patch with
173 When submitting a patch make sure to use
198 These legal notices prevent us from being able to accept your patch,
207 When you've reviewed a patch on the mailing list, please be unambiguous
228 which tells the patch author that the patch can be committed, as long
236 There are three ways to nominate a patch for inclusion in the stable branch and
242 <li> Forwarding the patch from the mesa-dev@ mailing list.
246 Note: resending patch identical to one on mesa-dev@ or one that differs only
269 This "CC" syntax for patch nomination will cause patches to automatically be
272 won't have any negative effect on the patch nomination.
275 Note: by removing the tag [as the commit is pushed] the patch is
281 Alternatively, if one uses the "Fixes" tag as described in the "Patch formatting"
296   <li>Patch must conform with the <a href="#guidelines">Basic guidelines</a></li>
298   <li>Patch must have landed in master first. In case where the original
299   patch is too large and/or otherwise contradicts with the rules set within, a
306   respective fix(es) should be provided in the nominated patch.</li>
308   <li>Patch cannot be larger than 100 lines.</li>
313   <li>Patch must be a bug fix and not a new feature.
320   <li>Patch must be reviewed, For example, the commit message has Reviewed-by,
328 If the patch complies with the rules it will be
330 manager will reply to the patch in question stating why the patch has been
337 stable branches, for example, to drop a previously-picked patch that was later
370 <li> Add version to subject line of patch series in this case for the last 8
373     git send-email --subject-prefix="PATCH v4" HEAD~8
374     git send-email -v4 @~8 # shorter version, inherited from git format-patch