Date: Mon, 18 May 2015 14:04:17 -0400 (EDT) From: Benjamin Kaduk <bjk@freebsd.org> To: Patrick Kelsey <pkelsey@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re: Improvement to pthread_getspecific(3) Message-ID: <alpine.GSO.1.10.1505181403100.22210@multics.mit.edu> In-Reply-To: <CAD44qMW3=axQypv3x=03kLUOraawsUW7Q1SToCwhnvhfcFs%2BQQ@mail.gmail.com> References: <CAD44qMW3=axQypv3x=03kLUOraawsUW7Q1SToCwhnvhfcFs%2BQQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 May 2015, Patrick Kelsey wrote: > Hi, > > I'd like to make the attached improvement to pthread_getspecific(3), and > this is my first time through a man page edit/commit, so I have a couple of > questions and would like to catch whatever else I'm missing. > > 1. Attribution - I'm using a lightly edited line from > http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_getspecific.html > (edited to account for the fact that we do not document both > pthread_getspecific() and pthread_setspecific() in the same man page). I'm > assuming that this falls under whatever agreement covers the existing man > page (which was constructed in similar fashion), but there is currently no > attribution in pthread_getspecific(3) and I'm not aware of what agreement > may be in place that allows for this. I'm not aware of what agreement may be in place, either. In a somewhat related vein, I do note: .Sh STANDARDS The .Fn pthread_getspecific function conforms to .St -p1003.1-96 . > 2. Markup - should I be using .Pq instead of explicit parentheses? We do not have a strong preference for Pq over explicit parentheses, so I would leave them in. -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1505181403100.22210>