Lines Matching +full:commit +full:- +full:message

11 While Phabricator is a useful tool for some, the relevant -commits mailing list
14 to respond to free-form comments in mail sent to the commits list.
17 -------
24 to the relevant -commits mailing list. If you are not subscribed to the commit
32 ----------------------------------------
42 -----------------------------------------
57 * ``git diff -U999999 other-branch``
58 * ``svn diff --diff-cmd=diff -x -U999999``
68   in the form of a :ref:`commit message <commit messages>`.
71   for LLVM, add llvm-commits as a Subscriber; if your patch is for Clang,
72   add cfe-commits.
88 them to participate. Many people will see the email notification on cfe-commits
89 or llvm-commits, and if the subject line suggests the patch is something they
94 * Use ``svn blame`` and the commit log to find names of people who have
105 -------------------------------
118 *Revision Update History*. Most features are self descriptive - explore, and
121 Note that as e-mail is the system of reference for code reviews, and some
128 -------------------
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.
176 git-svn and Arcanist
179 …es that the git repository has been configured as described in :ref:`developers-work-with-git-svn`.
189 This will create a new branch called ``arcpatch-D<Revision>`` based on the
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
200   git merge --ff-only arcpatch-D<Revision>
206 -------------------
208 If you decide you should not commit the patch, you should explicitly abandon
211 comment. In the drop-down Action list, which defaults to "Comment," you should
216 ------
219 working on setting up a bug tracker, but you can email klimek-at-google-dot-com
220 and chandlerc-at-gmail-dot-com and CC the llvm-dev mailing list with questions
224 on an `llvm-reviews GitHub project`_ where folks can hack on it and post pull
225 requests. We're looking into what the right long-term hosting for this is, but
234 .. _llvm-reviews GitHub project: https://github.com/r4nt/llvm-reviews/