Author: Aaron Ballman
Date: 2020-03-17T16:33:28-04:00
New Revision: 83989e69415e4064676150c62aefbce8ac0c61bf

URL: 
https://github.com/llvm/llvm-project/commit/83989e69415e4064676150c62aefbce8ac0c61bf
DIFF: 
https://github.com/llvm/llvm-project/commit/83989e69415e4064676150c62aefbce8ac0c61bf.diff

LOG: Don't call anyone lazy in the documentation.

Added: 
    

Modified: 
    clang/docs/HowToSetupToolingForLLVM.rst

Removed: 
    


################################################################################
diff  --git a/clang/docs/HowToSetupToolingForLLVM.rst 
b/clang/docs/HowToSetupToolingForLLVM.rst
index 58f10cfeffc1..cbe15abaab3b 100644
--- a/clang/docs/HowToSetupToolingForLLVM.rst
+++ b/clang/docs/HowToSetupToolingForLLVM.rst
@@ -37,7 +37,7 @@ make a build directory and run CMake from it:
 If you want to use clang instead of GCC, you can add
 ``-DCMAKE_C_COMPILER=/path/to/clang -DCMAKE_CXX_COMPILER=/path/to/clang++``.
 You can also use ``ccmake``, which provides a curses interface to configure
-CMake variables for lazy people.
+CMake variables.
 
 As a result, the new ``compile_commands.json`` file should appear in the
 current directory. You should link it to the LLVM source tree so that


        
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to