[rtems-docs commit] eng: Clarify "Coding Conventions" introduction

Sebastian Huber sebh at rtems.org
Wed Nov 11 06:44:38 UTC 2020


Module:    rtems-docs
Branch:    master
Commit:    b0b6c0cdd585ecb5bfafdc30e195d416e70a081d
Changeset: http://git.rtems.org/rtems-docs/commit/?id=b0b6c0cdd585ecb5bfafdc30e195d416e70a081d

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Thu Nov  5 19:39:57 2020 +0100

eng: Clarify "Coding Conventions" introduction

---

 eng/coding-conventions.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/eng/coding-conventions.rst b/eng/coding-conventions.rst
index 5dd8df5..e34cd74 100644
--- a/eng/coding-conventions.rst
+++ b/eng/coding-conventions.rst
@@ -9,11 +9,11 @@
 Coding Conventions
 ******************
 
-The style of RTEMS is generally consistent in the core areas.
-This page attempts to capture generally accepted practices.
-When in doubt, consult the code around you or look in cpukit/rtems.
-See the sister page `Doxygen Recommendations <https://devel.rtems.org/wiki/Developer/Coding/Doxygen>`_.
-for examples that illustrate style rules and Doxygen usage.
+The style of RTEMS is generally consistent in the core areas.  This section
+attempts to capture generally accepted practices.  When in doubt, consult the
+code around you, look in the RTEMS sources in the directories
+:file:`cpukit/include/rtems/score` and :file:`cpukit/score`, or ask on the
+:r:list:`devel`.
 
 Source Documentation
 --------------------



More information about the vc mailing list