[llvm] r284412 - [doc] use double `` to prevent html output of merging double dash

Mehdi Amini via llvm-commits llvm-commits at lists.llvm.org
Mon Oct 17 12:23:19 PDT 2016


Author: mehdi_amini
Date: Mon Oct 17 14:23:19 2016
New Revision: 284412

URL: http://llvm.org/viewvc/llvm-project?rev=284412&view=rev
Log:
[doc] use double `` to prevent html output of merging double dash

Modified:
    llvm/trunk/docs/Proposals/GitHubMove.rst

Modified: llvm/trunk/docs/Proposals/GitHubMove.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/Proposals/GitHubMove.rst?rev=284412&r1=284411&r2=284412&view=diff
==============================================================================
--- llvm/trunk/docs/Proposals/GitHubMove.rst (original)
+++ llvm/trunk/docs/Proposals/GitHubMove.rst Mon Oct 17 14:23:19 2016
@@ -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




More information about the llvm-commits mailing list