[llvm] ea4ec17 - update of the llvm doc: we moved to git
Sylvestre Ledru via llvm-commits
llvm-commits at lists.llvm.org
Sun Mar 22 14:36:36 PDT 2020
Author: Sylvestre Ledru
Date: 2020-03-22T22:36:21+01:00
New Revision: ea4ec17208062acaf4ec8f569293566994a02933
URL: https://github.com/llvm/llvm-project/commit/ea4ec17208062acaf4ec8f569293566994a02933
DIFF: https://github.com/llvm/llvm-project/commit/ea4ec17208062acaf4ec8f569293566994a02933.diff
LOG: update of the llvm doc: we moved to git
Added:
Modified:
llvm/docs/Docker.rst
llvm/docs/FAQ.rst
llvm/docs/Frontend/PerformanceTips.rst
llvm/docs/GettingStartedVS.rst
llvm/docs/HowToSubmitABug.rst
llvm/docs/Packaging.rst
Removed:
################################################################################
diff --git a/llvm/docs/Docker.rst b/llvm/docs/Docker.rst
index 5a42cbe698da..5a61ff988b05 100644
--- a/llvm/docs/Docker.rst
+++ b/llvm/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,
diff --git a/llvm/docs/FAQ.rst b/llvm/docs/FAQ.rst
index 6ce6051e1f65..99eeff6850a8 100644
--- a/llvm/docs/FAQ.rst
+++ b/llvm/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
-<http://llvm.org/svn/llvm-project/llvm/trunk/LICENSE.TXT>`_.
+follow the conditions listed in the `Apache License v2.0 with LLVM Exceptions
+<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?
diff --git a/llvm/docs/Frontend/PerformanceTips.rst b/llvm/docs/Frontend/PerformanceTips.rst
index 3c290964723b..f9e23fdbf885 100644
--- a/llvm/docs/Frontend/PerformanceTips.rst
+++ b/llvm/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.
diff --git a/llvm/docs/GettingStartedVS.rst b/llvm/docs/GettingStartedVS.rst
index 7507f97bac83..04fe0d4463e4 100644
--- a/llvm/docs/GettingStartedVS.rst
+++ b/llvm/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
- 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``.
+ *Note:* some regression tests require Unix-style line ending (``\n``).
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
diff --git a/llvm/docs/HowToSubmitABug.rst b/llvm/docs/HowToSubmitABug.rst
index d276ee8681f3..ac28f290bbdd 100644
--- a/llvm/docs/HowToSubmitABug.rst
+++ b/llvm/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!
diff --git a/llvm/docs/Packaging.rst b/llvm/docs/Packaging.rst
index 7c2dc956128e..176e5b391229 100644
--- a/llvm/docs/Packaging.rst
+++ b/llvm/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.
More information about the llvm-commits
mailing list