Lines Matching full:commit
24 to the relevant -commits mailing list. If you are not subscribed to the commit
68 in the form of a :ref:`commit message <commit messages>`.
94 * Use ``svn blame`` and the commit log to find names of people who have
132 method you follow it is recommend that your commit message ends with the line:
142 context. This also allows Phabricator to detect the commit, close the
143 review, and add a link from the review to the commit.
147 ``Differential Revision`` line (as the last line) to the commit message
152 and place it in the commit message. Several methods of using Arcanist to commit
153 code are given below. If you do not wish to use Arcanist then simply commit
156 Note that if you commit the change without using Arcanist and forget to add the
157 ``Differential Revision`` line to your commit message then it is recommended
171 arc commit --revision D<Revision>
174 copy. The second command will commit this revision to trunk.
190 current ``master`` and will create a commit corresponding to ``D<Revision>`` with a
191 commit message derived from information in the Phabricator review.
193 Check you are happy with the commit message and amend it if necessary. Now switch to
194 the ``master`` branch and add the new commit to it and commit it to trunk. This
208 If you decide you should not commit the patch, you should explicitly abandon
