RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-11-24 04:09:47 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Correct spelling of Git.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@178254 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Thomas Schwinge 2013-03-28 18:06:20 +00:00
parent 30509ee8a3
commit 7f5f06b818
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/CMake.rst
View File

@ -204,7 +204,7 @@ LLVM-specific variables
tests.
**LLVM_APPEND_VC_REV**:BOOL
Append version control revision info (svn revision number or git revision id)
Append version control revision info (svn revision number or Git revision id)
to LLVM version string (stored in the PACKAGE_VERSION macro). For this to work
cmake must be invoked before the build. Defaults to OFF.

10
docs/GettingStarted.rst
View File

@ -521,13 +521,13 @@ By placing it in the ``llvm/projects``, it will be automatically configured by
the LLVM configure script as well as automatically updated when you run ``svn
update``.
GIT mirror
Git Mirror
----------
GIT mirrors are available for a number of LLVM subprojects. These mirrors sync
Git mirrors are available for a number of LLVM subprojects. These mirrors sync
automatically with each Subversion commit and contain all necessary git-svn
marks (so, you can recreate git-svn metadata locally). Note that right now
mirrors reflect only ``trunk`` for each project. You can do the read-only GIT
mirrors reflect only ``trunk`` for each project. You can do the read-only Git
clone of LLVM via:
.. code-block:: console
@ -642,7 +642,7 @@ To set up clone from which you can submit code using ``git-svn``, run:
Likewise for compiler-rt and test-suite.
To update this clone without generating git-svn tags that conflict with the
upstream git repo, run:
upstream Git repo, run:
.. code-block:: console
@ -660,7 +660,7 @@ This leaves your working directories on their master branches, so you'll need to
parent branch.
For those who wish to be able to update an llvm repo in a simpler fashion,
consider placing the following git script in your path under the name
consider placing the following Git script in your path under the name
``git-svnup``:
.. code-block:: bash