update of the llvm doc: we moved to git

docs/Docker.rst

@@ -51,7 +51,7 @@ Overview
 The ``llvm/utils/docker`` folder contains Dockerfiles and simple bash scripts to
 serve as a basis for anyone who wants to create their own Docker image with
 LLVM components, compiled from sources. The sources are checked out from the
-upstream svn repository when building the image.
+upstream git repository when building the image.
 
 The resulting image contains only the requested LLVM components and a few extra
 packages to make the image minimally useful for C++ development, e.g. libstdc++
@@ -68,7 +68,7 @@ Usage
 =====
 The ``llvm/utils/build_docker_image.sh`` script provides a rather high degree of
 control on how to run the build. It allows you to specify the projects to
-checkout from svn and provide a list of CMake arguments to use during when
+checkout from git and provide a list of CMake arguments to use during when
 building LLVM inside docker container.
 
 Here's a very simple example of getting a docker image with clang binary,

docs/FAQ.rst

@@ -12,8 +12,8 @@ License
 Can I modify LLVM source code and redistribute the modified source?
 -------------------------------------------------------------------
 Yes.  The modified source distribution must retain the copyright notice and
-follow the conditions listed in the `LLVM license
+follow the conditions listed in the `Apache License v2.0 with LLVM Exceptions
-<http://llvm.org/svn/llvm-project/llvm/trunk/LICENSE.TXT>`_.
+<https://github.com/llvm/llvm-project/blob/master/llvm/LICENSE.TXT>`_.
 
 
 Can I modify the LLVM source code and redistribute binaries or other tools based on it, without redistributing the source?

docs/Frontend/PerformanceTips.rst

@@ -27,7 +27,7 @@ can often be useful to write a quick C program with the semantics you're trying
 to model and see what decisions Clang's IRGen makes about what IR to emit.
 Studying Clang's CodeGen directory can also be a good source of ideas.  Note
 that Clang and LLVM are explicitly version locked so you'll need to make sure
-you're using a Clang built from the same svn revision or release as the LLVM
+you're using a Clang built from the same git revision or release as the LLVM
 library you're using.  As always, it's *strongly* recommended that you track
 tip of tree development, particularly during bring up of a new project.
 

docs/GettingStartedVS.rst

@@ -74,15 +74,12 @@ Here's the short story for getting up and running quickly with LLVM:
          (*or use WinZip*)
       3. ``cd llvm``
 
-   * With anonymous Subversion access:
+   * With git access:
 
-     *Note:* some regression tests require Unix-style line ending (``\n``). To
+     *Note:* some regression tests require Unix-style line ending (``\n``).
-     pass all regression tests, please add two lines *enable-auto-props = yes*
-     and *\* = svn:mime-type=application/octet-stream* to
-     ``C:\Users\<username>\AppData\Roaming\Subversion\config``.
 
       1. ``cd <where-you-want-llvm-to-live>``
-      2. ``svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm``
+      2. ``git clone https://github.com/llvm/llvm-project.git llvm``
       3. ``cd llvm``
 
 5. Use `CMake <http://www.cmake.org/>`_ to generate up-to-date project files:
@@ -103,7 +100,7 @@ Here's the short story for getting up and running quickly with LLVM:
    * See the :doc:`LLVM CMake guide <CMake>` for detailed information about
      how to configure the LLVM build.
    * CMake generates project files for all build types. To select a specific
-     build type, use the Configuration manager from the VS IDE or the 
+     build type, use the Configuration manager from the VS IDE or the
      ``/property:Configuration`` command line option when using MSBuild.
    * By default, the Visual Studio project files generated by CMake use the
      32-bit toolset. If you are developing on a 64-bit version of Windows and

docs/HowToSubmitABug.rst

@@ -26,7 +26,7 @@ contain the following information:
 
 * All information necessary to reproduce the problem.
 * The reduced test-case that triggers the bug.
-* The location where you obtained LLVM (if not from our Subversion
+* The location where you obtained LLVM (if not from our Git
   repository).
 
 Thanks for helping us make LLVM better!

docs/Packaging.rst

@@ -38,7 +38,7 @@ versions of LLVM in parallel.  The following configure flags are relevant:
     should turn it back on to let users debug their programs.
 
 ``--enable-optimized``
-    (For svn checkouts) Builds LLVM with ``-O2`` and, by default, turns off
+    (For git checkouts) Builds LLVM with ``-O2`` and, by default, turns off
     debug symbols.  Also available by setting ``ENABLE_OPTIMIZED=0|1`` in
     ``make``'s environment.  This defaults to enabled when not in a
     checkout.