Lines Matching full:repository
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
174 repository. Not all bots have to migrate at this point, but it'll help
176 5. Update Phabricator to pick up commits from the GitHub repository.
180 repository.
194 10. Switch the SVN repository to read-only and allow pushes to the GitHub repository.
201 13. Archive the SVN repository.
205 GitHub Repository Description
211 The LLVM git repository hosted at https://github.com/llvm/llvm-project contains all
213 mimics an export of the current SVN repository, with each sub-project having its
233 Finally, the monorepo maintains the property of the existing SVN repository that
278 * Using the monolithic repository may add overhead for those contributing to a
285 * Using the monolithic repository may add overhead for those *integrating* a
306 how end-users or developers would interact with the repository for
337 constraints. First, you could just clone the full repository:
420 The repository contains natively the source for every sub-projects at the right
440 separately in every individual repository. It would be possible to establish a
456 To update the repository to tip of trunk::
486 repository:
488 To update the repository to tip of trunk::
512 the native Git bisection script over the llvm repository, and use some scripting
513 to synchronize the clang repository to match the llvm revision.
561 # Make a repository which will become your final local mirror of the
673 above. Such an umbrella repository looks something like this::
681 some local umbrella repository state that is not a submodule update,
815 repository. The second pair item describes the path where trees for
818 Let's say your umbrella repository is actually the llvm repository and
821 pointing to some downstream repository. The submodule map file should
924 If such repositories participated in the umbrella repository used
975 Given this repository history::
1001 appear in an umbrella repository, a new tool will need to be