Lines Matching refs:SVN

30 from SVN hosted on our own servers to Git hosted on GitHub. We are not proposing
34 Policy, except that that a GitHub account will be required instead of SVN
50 the SVN server is either down or unresponsive.
60 SVN, CVS, or anything else. Websites like GitHub have changed the landscape
65 sources being stored in a SVN server, these developers are already using Git
66 through the Git-SVN integration.
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.
136 In contrast to SVN, Git makes branching easy. Git's commit history is
137 represented as a DAG, a departure from SVN's linear history. However, we propose
148 installed on every developer machine?) and prevents SVN access to the
164 2. Set up a read-only version of the GitHub project, mirroring our current SVN
194 10. Switch the SVN repository to read-only and allow pushes to the GitHub repository.
196 12. Mirror Git to SVN.
201 13. Archive the SVN repository.
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
268 Read/write SVN bridge
271 GitHub supports a read/write SVN bridge for its repositories.  However,
283    use the SVN bridge or the single-subproject Git mirrors. However, it's
289  * Preservation of the existing read/write SVN-based workflows relies on the
290    GitHub SVN bridge, which is an extra dependency. Maintaining this locks us
319   # direct SVN checkout
344 from someone who would check out all the projects with SVN today.
371 Note that today with SVN or git-svn, this step is not possible since the
452 SVN does not allow this use case, but developers that are currently using
508 SVN does not have builtin bisection support, but the single revision across