Fix #1068, rename doc to docs

.github/pull_request_template.md

@@ -29,6 +29,6 @@ Full name and company/organization/center of all contributors ("Personal" if ind
 - If NASA Civil Servant Employee or GSFC Contractor on SES II
   - Address/email/phone and contract/task information (if applicable) must be on file
 - Else if Company
-  - **HAND SIGNED** Company CLA must be on file (once per release): [OSAL Company CLA](../doc/GSC_18370_Corp_CLA_form_1219.pdf)
+  - **HAND SIGNED** Company CLA must be on file (once per release): [OSAL Company CLA](../docs/GSC_18370_Corp_CLA_form_1219.pdf)
 - Else if Individual
-  - **HAND SIGNED** Individual CLA must be on file (once per release): [OSAL Individual CLA](../doc/GSC_18370_Ind_CLA_form_1219.pdf)
+  - **HAND SIGNED** Individual CLA must be on file (once per release): [OSAL Individual CLA](../docs/GSC_18370_Ind_CLA_form_1219.pdf)

CMakeLists.txt

@@ -354,7 +354,7 @@ if (HAS_PARENT)
 else(HAS_PARENT)
     # In a standalone build, also add the documentation target(s)
     # Note that in a CFE/integrated build, it is expected this will be built separately.
-    add_subdirectory(doc/src doc)
+    add_subdirectory(docs/src docs)
 endif(HAS_PARENT)
 
 

README.md

@@ -161,7 +161,7 @@ the declarations, and generates a source file with stub definitions that rely on
 - Adds _new_ accessor functions APIs to get version strings and return the values of string macros defined in `osapi-version.h`.
   - The "simple" version currently `OS_VERSION` macro - this is the semantic version without any extra detail.  This is returned by `OS_GetVersion()`.
   - The "descriptive" version in `OS_VERSION_STRING` macro - this has extra detail like the most recent official release.  This is returned by `OS_GetVersionDescription()`.
-  - The release code name, now returned by `OS_GetVersionDescription()`.  
+  - The release code name, now returned by `OS_GetVersionDescription()`.
 - These accessor functions are the preferred way to get the OSAL version string, from now on users should avoid using the macro definitions as it is evaluated at OSAL library compile time, rather than application compile time, and thus will remain correct in the event that OSAL is relinked without recompiling the application.
 Adds `osapi-version.c` to implement these 3 calls and associated coverage test. This allows the version.c file to be auto-generated in the future.
 - See <https://github.com/nasa/osal/pull/835>
@@ -228,7 +228,7 @@ Adds `osapi-version.c` to implement these 3 calls and associated coverage test.
   - keep threads "attached" in POSIX, so they can be joined when deleted.
 - No longer triggers warning with OS_TaskExit() on VxWorks (see #645)
 - `OS_TaskDelete()` on POSIX does not return until the task has actually exited (see #642)
-- The chmod test is now skipped on VxWorks rather than failing. The `OS_FileChmod_Impl()` function now returns `OS_ERR_NOT_IMPLEMENTED` when run on a file system that does not have permissions, which in turn causes the unit test to be skipped rather than fail.   
+- The chmod test is now skipped on VxWorks rather than failing. The `OS_FileChmod_Impl()` function now returns `OS_ERR_NOT_IMPLEMENTED` when run on a file system that does not have permissions, which in turn causes the unit test to be skipped rather than fail.
 - Corrects a file handle leak.
 -  Add parameter check to `OS_SocketSendTo` and adjust coverage test to validate.
 - Replace `OS_fsBytesFree` and `OS_fsBlocksFree` with `OS_FileSysStatVolume`. This new API for getting stats on file system. Uses existing `OS_FileSysStatVolume_Impl` call and exposes it in the public API.
@@ -428,7 +428,7 @@ UT Hook functions now have the capability to get argument values by name, which
 - If `OSAL_EXT_SOURCE_DIR` cache variable is set, this location will be checked first for a BSP/OS implementation layer.
 - Implement `OS_GetResourceName()` and `OS_ForEachObjectOfType()`, which are new functions that allow for additional query capabilities. No impact to current behavior as the FSW does not currently use any of these new APIs.
 - A functional test enhancement to `bin-sem-test` which replicates the specific conditions for the observed bug to occur. Deletes the task calling `OS_BinSemTake()` and then attempts to use the semaphore after this.
-- Employ a `pthread` "cleanup handler" to handle the situation where a task is canceled during the `pthread_cond_wait()` call. This ensures that the `mutex` is unlocked as part of the cleanup, so other tasks may continue using the semaphore.    
+- Employ a `pthread` "cleanup handler" to handle the situation where a task is canceled during the `pthread_cond_wait()` call. This ensures that the `mutex` is unlocked as part of the cleanup, so other tasks may continue using the semaphore.
 - Change all initial `mutex` locking to be a finite "timed" wait rather than an infinite wait. In all cases, the condition variable is only held for brief periods of time and should be readily available. If a task blocks for a long time, this considers the mutex "broken" and aborts, thereby avoiding deadlock. This is a "contingency" fix in that if an exception or signal or other unknown/unhandled async event occurs that leaves the mutex permanently locked.
 - Adds the mutex to protect the timer callback `timecb` resource table.
 - See <https://github.com/nasa/osal/pull/482>
@@ -556,7 +556,7 @@ make
 make test
 ```
 
-See the [Configuration Guide](https://github.com/nasa/osal/blob/main/doc/OSAL-Configuration-Guide.md) for more information.
+See the [Configuration Guide](https://github.com/nasa/osal/blob/main/docs/OSAL-Configuration-Guide.md) for more information.
 
 See also the autogenerated user's guide: <https://github.com/nasa/cFS/blob/gh-pages/OSAL_Users_Guide.pdf>
 

doc/OSAL-Configuration-Guide.md → docs/OSAL-Configuration-Guide.md

@@ -56,7 +56,7 @@ These terms are identified as proper nouns and are capitalized.
 | MMU   |  Memory Management Unit. A piece of hardware that manages virtual memory systems.  It automatically translates addresses into physical addresses so that an application can  be linked with one set of addresses but actually reside in a different part of memory. |
 | Network | A connection between subsystems used for communication purposes.  |
 | Platform  | See "Hardware Platform" above.   |
-| User  | Anyone who interacts with the Software Application or system in its operational state.  A user can be a developer, a tester, an operator, or a maintainer. 
+| User  | Anyone who interacts with the Software Application or system in its operational state.  A user can be a developer, a tester, an operator, or a maintainer.
 
 # How to Configure, Build, and Run the OSAL
 
@@ -114,7 +114,7 @@ machine. The source distribution has the following directories:
 | `osal/src/bsp`                | The bsp directory contains the platform specific code for the OSAL as well  as code to make the OSAL run on a particular platform. Everything in  this directory is used to adapt the OSAL and Applications to a particular  hardware platform. This directory also contains the startup code for the  example programs. The included platforms are generic enough that they may be  easy to port to other platforms and processor architectures. For example:  The bsp/mcf5235-rtems board support package was ported to an ARM processor  running RTEMS with minimal effort.  |
 | `osal/src/os`                 | The os directory is the heart of the OSAL, containing the implementation of  the OSAL for each supported operating system. There is a sub-directory for  each supported operating system in this directory. The OSAL include files  are also contained in this directory (src/os/inc).  |
 | `osal/src/inc`                | The inc directory contains system wide include files that are used by the  OSAL on all platforms.  |
-| `osal/doc`                    | The doc directory contains the documentation and release notes for the OSAL. |
+| `osal/docs`                   | The docs directory contains the documentation and release notes for the OSAL. |
 
 
 The osal directory can go just about anywhere on a host development