[clang-tools-extra] r270033 - [clang-tidy] Fix/add style guide links.

[Alexander Kornienko via cfe-commits]

Author: alexfh
Date: Thu May 19 04:31:30 2016
New Revision: 270033

URL: http://llvm.org/viewvc/llvm-project?rev=270033&view=rev
Log:
[clang-tidy] Fix/add style guide links.

Thanks to Tim Halloran for the initial patch (http://reviews.llvm.org/D15089)!

Modified:
    clang-tools-extra/trunk/clang-tidy/google/GlobalNamesInHeadersCheck.h
    clang-tools-extra/trunk/docs/clang-tidy/checks/google-global-names-in-headers.rst
    clang-tools-extra/trunk/docs/clang-tidy/checks/google-readability-todo.rst
    clang-tools-extra/trunk/docs/clang-tidy/checks/google-runtime-int.rst

Modified: clang-tools-extra/trunk/clang-tidy/google/GlobalNamesInHeadersCheck.h
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/clang-tidy/google/GlobalNamesInHeadersCheck.h?rev=270033&r1=270032&r2=270033&view=diff
==============================================================================
--- clang-tools-extra/trunk/clang-tidy/google/GlobalNamesInHeadersCheck.h (original)
+++ clang-tools-extra/trunk/clang-tidy/google/GlobalNamesInHeadersCheck.h Thu May 19 04:31:30 2016
@@ -23,7 +23,7 @@ namespace readability {
 ///
 /// The check supports these options:
 ///   - `HeaderFileExtensions`: a comma-separated list of filename extensions
-///     of header files (The filename extensions should not contain "." prefix).
+///     of header files (the filename extensions should not contain "." prefix).
 ///     "h" by default.
 ///     For extension-less header files, using an empty string or leaving an
 ///     empty string between "," if there are other filename extensions.

Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/google-global-names-in-headers.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/docs/clang-tidy/checks/google-global-names-in-headers.rst?rev=270033&r1=270032&r2=270033&view=diff
==============================================================================
--- clang-tools-extra/trunk/docs/clang-tidy/checks/google-global-names-in-headers.rst (original)
+++ clang-tools-extra/trunk/docs/clang-tidy/checks/google-global-names-in-headers.rst Thu May 19 04:31:30 2016
@@ -5,3 +5,13 @@ google-global-names-in-headers
 
 Flag global namespace pollution in header files.
 Right now it only triggers on ``using`` declarations and directives.
+
+The check supports these options:
+  - `HeaderFileExtensions`: a comma-separated list of filename extensions
+    of header files (the filename extensions should not contain "." prefix).
+    "h" by default.
+    For extension-less header files, using an empty string or leaving an
+    empty string between "," if there are other filename extensions.
+
+The relevant style guide section is
+https://google.github.io/styleguide/cppguide.html#Namespaces.

Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/google-readability-todo.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/docs/clang-tidy/checks/google-readability-todo.rst?rev=270033&r1=270032&r2=270033&view=diff
==============================================================================
--- clang-tools-extra/trunk/docs/clang-tidy/checks/google-readability-todo.rst (original)
+++ clang-tools-extra/trunk/docs/clang-tidy/checks/google-readability-todo.rst Thu May 19 04:31:30 2016
@@ -5,4 +5,7 @@ google-readability-todo
 
 Finds TODO comments without a username or bug number.
 
+The relevant style guide section is
+https://google.github.io/styleguide/cppguide.html#TODO_Comments.
+
 Corresponding cpplint.py check: `readability/todo`

Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/google-runtime-int.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/docs/clang-tidy/checks/google-runtime-int.rst?rev=270033&r1=270032&r2=270033&view=diff
==============================================================================
--- clang-tools-extra/trunk/docs/clang-tidy/checks/google-runtime-int.rst (original)
+++ clang-tools-extra/trunk/docs/clang-tidy/checks/google-runtime-int.rst Thu May 19 04:31:30 2016
@@ -7,6 +7,6 @@ Finds uses of ``short``, ``long`` and ``
 with ``u?intXX(_t)?``.
 
 The corresponding style guide rule:
-https://google-styleguide.googlecode.com/svn/trunk/cppguide.html#Integer_Types.
+https://google.github.io/styleguide/cppguide.html#Integer_Types.
 
 Correspondig cpplint.py check: `runtime/int`.