| /llvm-project/llvm/cmake/modules/ |
| H A D | GenerateVersionFromVCS.cmake | 21 function(append_info name revision repository)
29 if(repository)
31 "#define ${name}_REPOSITORY \"${repository}\"\n")
41 set(repository ${LLVM_FORCE_VC_REPOSITORY}) variable
45 set(repository ${LLVM_FORCE_VC_REPOSITORY}) variable
48 set(repository ${${name}_VC_REPOSITORY}) variable
51 get_source_info("${${name}_SOURCE_DIR}" revision repository)
56 append_info(${name} "${revision}" "${repository}")
|
| H A D | VersionFromVCS.cmake | 6 function(get_source_info path revision repository)
48 message(SEND_ERROR "The git remote repository URL has an embedded \
60 message(SEND_ERROR "The git remote repository URL has an embedded \
67 set(${repository} ${git_output} PARENT_SCOPE)
69 set(${repository} ${path} PARENT_SCOPE)
|
| /llvm-project/clang/include/clang/Basic/ |
| H A D | Version.h | 22 /// Retrieves the repository path (e.g., Subversion path) that
27 /// Retrieves the repository path from which LLVM was built.
29 /// This supports LLVM residing in a separate repository from clang.
32 /// Retrieves the repository revision number (or identifier) from which
36 /// Retrieves the repository revision number (or identifier) from which
39 /// If Clang and LLVM are in the same repository, this returns the same
46 /// Retrieves the full repository version that is an amalgamation of
51 /// which includes the clang version number, the repository version,
60 /// number, the repository version, and the vendor tag.
|
| /llvm-project/flang/include/flang/Common/ |
| H A D | Version.h | 22 /// Retrieves the repository path (e.g., Git path) that
27 /// Retrieves the repository path from which LLVM was built.
29 /// This supports LLVM residing in a separate repository from flang.
32 /// Retrieves the repository revision number (or identifier) from which
36 /// Retrieves the repository revision number (or identifier) from which
39 /// If Flang and LLVM are in the same repository, this returns the same
43 /// Retrieves the full repository version that is an amalgamation of
48 /// which includes the flang version number, the repository version,
|
| /llvm-project/llvm/docs/Proposals/ |
| H A D | GitHubMove.rst | 29 This proposal relates only to moving the hosting of our source-code repository
73 * Inspect the repository history (blame, log, bisect) without Internet access.
75 integrate back to the main repository.
92 BitBucket: it offers read-write **SVN** access to the repository
95 were still canonically in an SVN repository.
103 The current SVN repository hosts all the LLVM sub-projects alongside each other.
138 to mandate making merge commits illegal in our canonical Git repository.
149 repository.
165 repository.
167 umbrella repository update (if the multirepo is selected) or the read-only
[all …]
|
| /llvm-project/clang-tools-extra/ |
| H A D | README.txt | 2 // Clang Tools repository
5 Welcome to the repository of extra Clang Tools. This repository holds tools
7 Clang frontend. These tools are kept in a separate "extra" repository to
10 All discussion regarding Clang, Clang-based tools, and code in this repository
|
| /llvm-project/llvm/docs/ |
| H A D | SupportPolicy.rst | 15 There are, however, other components within the main repository that either
18 or external projects. Those parts of the main repository don't always have
24 repository is beneficial to minimise the repetition of those changes in all
30 main repository (``llvm-project``) and not the other repositories in our git
39 The core tier encompasses all of the code in the main repository that is
77 alternative paths (work-in-progress replacements) in the same repository, as
98 * Main repository projects that don't get released or regularly tested.
107 * Have a clear benefit for residing in the main repository, catering to an
171 so it remains in the repository with the assumption that it could still be
174 For code to remain in the repository, its presence must not impose an undue
|
| H A D | GitHub.rst | 23 llvm/llvm-project repository otherwise, please use a fork (see below). User branches that
96 to your fork and "upstream" points to the main llvm-project repository.
152 If you do not have write permissions for the repository, the merge button in
350 First follow the instructions to [fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo?tool=webui#forking-a-repository).
352 Next follow the instructions to [clone your forked repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo?tool=webui#cloning-your-forked-repository).
354 Once you've cloned your forked repository,
|
| /llvm-project/clang/utils/analyzer/ |
| H A D | SATestAdd.py | 5 the Repository Directory.
8 Assumes it's being run from the Repository Directory.
9 The project directory should be added inside the Repository Directory and
26 repository directly.
|
| /llvm-project/llvm/utils/docker/ |
| H A D | build_docker_image.sh | 27 -d|--docker-repository docker repository for the image
48 Required options: --source and --docker-repository, at least one
89 -d|--docker-repository)
154 echo "Required argument missing: --docker-repository"
|
| /llvm-project/clang/tools/ |
| H A D | CMakeLists.txt | 43 # We support checking out the clang-tools-extra repository into the 'extra'
45 # on top of the Clang tooling platform. We keep them in a separate repository
46 # to keep the primary Clang repository small and focused.
|
| /llvm-project/clang/docs/ |
| H A D | ClangTools.rst | 42 the tools are developed in a side repository to provide easy separation
44 libraries in the side repository, as we want to carefully review and
48 Regardless of which repository Clang Tools' code resides in, the
56 The core set of Clang tools that are within the main repository are
87 As various categories of Clang Tools are added to the extra repository,
|
| /llvm-project/.github/workflows/ |
| H A D | issue-write.yml | 70 repository(owner: $repo_owner, name: $repo_name) {
99 if (!gql_result.repository.ref) {
103 console.log(gql_result.repository.ref.associatedPullRequests.nodes);
106 gql_result.repository.ref.associatedPullRequests.nodes.forEach((pr) => {
|
| H A D | scorecard.yml | 25 if: github.repository == 'llvm/llvm-project'
45 # - Allows the repository to include the Scorecard badge.
50 # format to the repository Actions tab.
|
| H A D | pr-code-format.yml | 19 if: github.repository == 'llvm/llvm-project'
45 repository: ${{ github.repository }}
|
| H A D | release-binaries.yml | |
| H A D | issue-release-workflow.yml | 40 (github.repository == 'llvm/llvm-project') &&
47 repository: llvm/llvm-project
|
| H A D | new-prs.yml | 29 (github.repository == 'llvm/llvm-project') &&
66 always() && github.repository == 'llvm/llvm-project' &&
|
| /llvm-project/lldb/examples/test/ |
| H A D | usage-lldb-loggings | 15 Repository Root: https://johnny@llvm.org/svn/llvm-project
16 Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8
76 Repository Root: https://johnny@llvm.org/svn/llvm-project
77 Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8
|
| H A D | usage-pre-post-flight | 14 Repository Root: https://johnny@llvm.org/svn/llvm-project
15 Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8
|
| /llvm-project/clang-tools-extra/docs/ |
| H A D | clang-doc.rst | 110 --repository=<string> -
111 URL of repository that hosts code.
120 - ``repository``
|
| /llvm-project/libcxx/utils/ |
| H A D | clang-format-merge-driver.sh | 8 # The script is installed by running the following from the root of your repository:
25 # The path of the file in the repository.
|
| /llvm-project/clang-tools-extra/unittests/clang-doc/ |
| H A D | HTMLGeneratorTest.cpp | 179 ClangDocContext CDCtx = getClangDocContext({}, "http://www.repository.com"); in TEST()
195 <a href="http://www.repository.com/dir/test.cpp#10">10</a> in TEST()
197 <a href="http://www.repository.com/dir/test.cpp">test.cpp</a> in TEST()
302 ClangDocContext CDCtx = getClangDocContext({}, "https://www.repository.com"); in TEST()
350 ClangDocContext CDCtx = getClangDocContext({}, "www.repository.com"); in TEST()
378 <a href="https://www.repository.com/test.cpp#10">10</a> in TEST()
380 <a href="https://www.repository.com/test.cpp">test.cpp</a> in TEST()
|
| /llvm-project/llvm/utils/git/ |
| H A D | github-automation.py | 34 1. Open a [pull request](https://github.com/llvm/llvm-project/pulls) to the [upstream repository](https://github.com/llvm/llvm-project) on GitHub. Detailed instructions can be found [in GitHub's documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). [Mention](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this issue in the description of the pull request.
233 If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using `@` followed by their GitHub username.
384 def repo(self) -> github.Repository.Repository:
541 self, repo: github.Repository.Repository, head: str
664 help="The GitHub repository that we are working with in the form of <owner>/<repo> (e.g. llvm/llvm-project)",
696 help="GitHub authentication token to use for the repository where new branches will be pushed. Defaults to TOKEN.",
551 check_if_pull_request_exists( self, repo: github.Repository.Repository, head: str ) global() argument
|
| /llvm-project/polly/docs/ |
| H A D | TipsAndTricks.rst | 49 LLVM has a single repository that contains all projects. It can be cloned at:
51 git repository is explained here
|