Searched +full:docs +full:- +full:changed +full:- +full:subprojects (Results 1 – 6 of 6) sorted by relevance
| /llvm-project/.github/workflows/ |
| H A D | docs.yml | 4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clan
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | ReleaseNotes.rst | |
| H A D | MyFirstTypoFix.rst | 26 - know how to use an editor,
28 - have basic C++ knowledge,
30 - know how to install software on your system,
32 - are comfortable with the command line,
34 - have basic knowledge of git.
38 -----
[all...] |
| H A D | DeveloperPolicy.rst | 18 contributions. This policy covers all llvm.org subprojects, including Clang,
30 policies <copyright-license-patents>` with contributors to the project.
33 contributing one-off patches can do so in an informal way by sending them to the
34 `llvm-commits mailing list
35 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
42 always welcome `one-off patches`_ from people who do not routinely contribute to
49 ---
[all...] |
| H A D | CodingStandards.rst | 14 particularly important for large-scale code bases that follow a library-based
35 want patches that do large-scale reformatting of existing code. On the other
48 environment restrictions, historical restrictions, or due to third-party source
53 For automation, build-systems and utility scripts Python is preferred and
57 -----
[all...] |
| /llvm-project/llvm/docs/Proposals/ |
| H A D | GitHubMove.rst | 22 infrastructure) will continue to work with a Git-based LLVM.
29 This proposal relates only to moving the hosting of our source-code repository
31 using GitHub's issue tracker, pull-requests, or code-review.
35 username/password-hash.
41 ----------------
57 --------
60 SVN, CVS, or anything else. Websites like GitHub have changed the landscape
66 through the Git-SVN integration.
82 -----------
85 projects. Any of these could replace the code-hosting infrastructure that we
[all …]
|