Lines Matching full:commits

32 `llvm-commits mailing list
33 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
55 subscribe to the "commits" mailing list for the subproject you're interested in,
56 such as `llvm-commits
57 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_, `cfe-commits
58 <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_, or `lldb-commits
59 <http://lists.llvm.org/mailman/listinfo/lldb-commits>`_.  Reading the
60 "commits" list and paying attention to changes being made by others is a good
269 bots will directly email you if a group of commits that included yours caused a
273 Commits that violate these quality standards (e.g. are very broken) may be
300 * The title should be concise. Because all commits are emailed to the list with
334 omissions can be handled by sending a reply to the commits mailing list.
345 #. The full name and email address you want message to llvm-commits to come
369    approval, submit a `patch`_ to `llvm-commits
370    <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_. When approved,
381    responsibility for), with the proviso that such commits must not break the
382    build.  This is a "trust but verify" policy, and commits of this nature are