[PATCH] Add "Inter-process Communication" chapter to the glibc manual.

[Carlos O'Donell]

On 02/26/2014 03:47 AM, Florian Weimer wrote:
> On 02/26/2014 05:54 AM, Carlos O'Donell wrote:
> 
>> +The @glibcadj{} implements the semaphore APIs as defined in POSIX and
>> +System V. Semaphores can be used by multiple processes to coordinate shared
>> +resources. The following is a complete list of the semaphore functions provided
>> +by @theglibc{}.
> 
> I think the GNU style calls for two spaces at the end of a sentence.

It is, but AFAIK makes no difference in the output since such formatting
is handled by texinfo (the pdf shows no difference).

v2.
- Use two spaces after a period.

[Incremental diff]

diff --git a/manual/ipc.texi b/manual/ipc.texi
index bf867b8..f8700b0 100644
--- a/manual/ipc.texi
+++ b/manual/ipc.texi
@@ -11,9 +11,9 @@ This chapter describes the @glibcadj{} inter-process communication primitives.
 @node Semaphores
 @section Semaphores
 
-The @glibcadj{} implements the semaphore APIs as defined in POSIX.1-2001 and
-System V. Semaphores can be used by multiple processes to coordinate shared
-resources. The following is a complete list of the semaphore functions provided
+The @glibcadj{} implements the semaphore APIs as defined in POSIX and
+System V.  Semaphores can be used by multiple processes to coordinate shared
+resources.  The following is a complete list of the semaphore functions provided
 by @theglibc{}.
 
 @c Need descriptions for all of these functions.
@@ -22,9 +22,9 @@ by @theglibc{}.
 @deftypefun int semctl (int @var{semid}, int @var{semnum}, int @var{cmd});
 @safety{@prelim{}@mtsafe{}@assafe{}@acunsafe{@acucorrupt{/linux}}}
 @c syscall(ipc) ok
-@c 
+@c
 @c AC-unsafe because we need to translate the new kernel
-@c semid_ds buf into the userspace layout. Cancellation
+@c semid_ds buf into the userspace layout.  Cancellation
 @c at that point results in an inconsistent userspace
 @c semid_ds.
 @end deftypefun
@@ -87,9 +87,9 @@ by @theglibc{}.
 @c atomic_increment (nwaiters) acucorrupt
 @c
 @c Given the use atomic operations this function seems
-@c to be AS-safe. It is AC-unsafe because there is still
+@c to be AS-safe.  It is AC-unsafe because there is still
 @c a window between atomic_decrement and the pthread_push
-@c of the handler that undoes that operation. A cancellation
+@c of the handler that undoes that operation.  A cancellation
 @c at that point would fail to remove the process from the
 @c waiters count.
 @end deftypefun
---

Cheers,
Carlos.