summaryrefslogtreecommitdiffstats
path: root/docs/Proposals
diff options
context:
space:
mode:
authorMehdi Amini <mehdi.amini@apple.com>2016-10-17 19:23:19 +0000
committerMehdi Amini <mehdi.amini@apple.com>2016-10-17 19:23:19 +0000
commit303d287af0ec4792517e121e1292b987359e4b06 (patch)
tree5d344caa2312cd394c4d07cd06c1ed55b23ff7af /docs/Proposals
parent6b54de2a5a1b879771a9b6544fc5dc64b2705b92 (diff)
[doc] use double `` to prevent html output of merging double dash
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@284412 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/Proposals')
-rw-r--r--docs/Proposals/GitHubMove.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/Proposals/GitHubMove.rst b/docs/Proposals/GitHubMove.rst
index fbb1b040ce28..c1bdfb359289 100644
--- a/docs/Proposals/GitHubMove.rst
+++ b/docs/Proposals/GitHubMove.rst
@@ -123,9 +123,9 @@ past discussions about Git:
- "Sequential IDs are important for LNT and llvmlab bisection tool." [MatthewsRevNum]_.
However, Git can emulate this increasing revision number:
-`git rev-list --count <commit-hash>`. This identifier is unique only within a
-single branch, but this means the tuple `(num, branch-name)` uniquely identifies
-a commit.
+``git rev-list --count <commit-hash>``. This identifier is unique only
+within a single branch, but this means the tuple `(num, branch-name)` uniquely
+identifies a commit.
We can thus use this revision number to ensure that e.g. `clang -v` reports a
user-friendly revision number (e.g. `master-12345` or `4.0-5321`), addressing