Lines Matching full:commit
26 <li><a href="#nominations">Nominating a commit for a stable branch</a>
70 for Sandybridge (commit 077d01b6). There is no documentation saying this
205 <h2 id="nominations">Nominating a commit for a stable branch</h2>
213 <li> Sending the commit ID (as seen in master branch) to the mesa-stable@ mailing list.
226 If you want a commit to be applied to a stable branch,
227 you should add an appropriate note to the commit message.
240 the commit for the most-recently-created stable branch. It is only necessary
242 examples above), if you want to nominate the commit for an older stable
243 branch. And, as in these examples, you can nominate the commit for the older
244 branch in addition to the more recent branch, or nominate the commit
253 Note: by removing the tag [as the commit is pushed] the patch is
268 <code>git cherry-pick -x <commit></code>. The <code>-x</code> option is
269 important so that the picked patch references the commit ID of the original
291 <li>Patch is not a fix. For example, a commit that moves code around with no
294 <li>Patch fix is not clearly described. For example, a commit message
298 <li>Patch has not obviously been reviewed, For example, the commit message
348 <li>Apply a fixup to commit FOO.
351 git commit --fixup=FOO
