[Lldb-commits] [lldb] f3e6f85 - [lldb][NFC] Remove a stray unicode character in the LLDB test docs
Raphael Isemann via lldb-commits
lldb-commits at lists.llvm.org
Fri Apr 23 04:20:44 PDT 2021
Author: Raphael Isemann
Date: 2021-04-23T13:20:10+02:00
New Revision: f3e6f856c2905362f54acebc5ef500df10cb06fa
URL: https://github.com/llvm/llvm-project/commit/f3e6f856c2905362f54acebc5ef500df10cb06fa
DIFF: https://github.com/llvm/llvm-project/commit/f3e6f856c2905362f54acebc5ef500df10cb06fa.diff
LOG: [lldb][NFC] Remove a stray unicode character in the LLDB test docs
There was a U+2028 character in this line (a special paragraph separator).
Added:
Modified:
lldb/docs/resources/test.rst
Removed:
################################################################################
diff --git a/lldb/docs/resources/test.rst b/lldb/docs/resources/test.rst
index 2c08ddde28dc4..4c70e131f0d73 100644
--- a/lldb/docs/resources/test.rst
+++ b/lldb/docs/resources/test.rst
@@ -156,7 +156,7 @@ test, the API test also allow for much more complex scenarios when it comes to
building inferiors. Every test has its own ``Makefile``, most of them only a
few lines long. A shared ``Makefile`` (``Makefile.rules``) with about a
thousand lines of rules takes care of most if not all of the boiler plate,
-while individual make files can be used to build more advanced tests.
+while individual make files can be used to build more advanced tests.
Here's an example of a simple ``Makefile`` used by the example test.
More information about the lldb-commits
mailing list