[libcxx-commits] [libcxx] [libc++][docs][NFC] Fix inline code style - use double backticks (PR #108974)
Hristo Hristov via libcxx-commits
libcxx-commits at lists.llvm.org
Tue Sep 17 06:23:59 PDT 2024
https://github.com/H-G-Hristov created https://github.com/llvm/llvm-project/pull/108974
This is an apparrent omission. Single backick (Markdown style) was used instead of double backtick for inline code style.
>From 48692e38497a7e20bcfc2f0c2eca720ab7bcd2f9 Mon Sep 17 00:00:00 2001
From: Hristo Hristov <hghristov.rmm at gmail.com>
Date: Tue, 17 Sep 2024 16:23:24 +0300
Subject: [PATCH] [libc++][docs][NFC] Fix inline code style - use double
backticks
This is an apparrent omission. Single backick (Markdown style) was used instead of double backtick for inline code style.
---
libcxx/docs/Contributing.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libcxx/docs/Contributing.rst b/libcxx/docs/Contributing.rst
index f81c537e00c243..b15fc88943d59b 100644
--- a/libcxx/docs/Contributing.rst
+++ b/libcxx/docs/Contributing.rst
@@ -168,7 +168,7 @@ sure you don't forget anything:
- Did you add the relevant feature test macro(s) for your feature? Did you update the ``generate_feature_test_macro_components.py`` script with it?
- Did you run the ``libcxx-generate-files`` target and verify its output?
-- If needed, did you add `_LIBCPP_PUSH_MACROS` and `_LIBCPP_POP_MACROS` to the relevant headers?
+- If needed, did you add ``_LIBCPP_PUSH_MACROS`` and ``_LIBCPP_POP_MACROS`` to the relevant headers?
The review process
==================
More information about the libcxx-commits
mailing list