Changelog for fork/subprocess interoperability

Author: nspark

content/backmatter.tex

@@ -668,6 +668,10 @@ \section{Version 1.6}
     \openshmem[1.5] Table 10, and clarified the types, names, and supporting
     operations for team-based reductions.
 \ChangelogRef{teamreducetypes}%
+%
+\item Clarified the interaction of the \openshmem library with
+  subprocess creation.%
+  \ChangelogRef{subsec:subprocess}%
 \end{itemize}
 
 \section{Version 1.5}
@@ -742,7 +746,7 @@ \section{Version 1.5}
   subsec:shmem_reductions}%
 %
 \item Clarified interoperability of \openshmem with other programming models.
-\ChangelogRef{sec:interoperability}%
+\ChangelogRef{sec:interoperability, subsec:mpi}%
 %
 \item Clarified restrictions on using pointers to symmetric objects.
 \ChangelogRef{

content/interoperability.tex

@@ -7,7 +7,7 @@ \chapter{Interoperability with Other Programming Models}\label{sec:interoperabil
 and advice to \openshmem library users and developers that may improve the portability
 and performance of hybrid programs.
 
-\section{Subprocesses}
+\section{Subprocesses}\label{subsec:subprocess}
 
 In some cases, an \openshmem application may be used to create or
 orchestrate other processes, which can be created through a number of
@@ -48,7 +48,7 @@ \section{Subprocesses}
 }
 
 
-\section{MPI Interoperability}
+\section{MPI Interoperability}\label{subsec:mpi}
 
 \openshmem and \ac{MPI} are two commonly used parallel programming models for
 distributed-memory systems. The user can choose to utilize both models in the same program