From owner-freebsd-doc@FreeBSD.ORG Mon May 18 18:04:28 2015 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBD8486F; Mon, 18 May 2015 18:04:28 +0000 (UTC) Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 50D501CBF; Mon, 18 May 2015 18:04:27 +0000 (UTC) X-AuditID: 12074425-f79ca6d000000e5e-95-555a29a4fe08 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 16.64.03678.4A92A555; Mon, 18 May 2015 14:04:20 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id t4II4JVC017660; Mon, 18 May 2015 14:04:20 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id t4II4Il1001039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 18 May 2015 14:04:19 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id t4II4HJd012494; Mon, 18 May 2015 14:04:17 -0400 (EDT) Date: Mon, 18 May 2015 14:04:17 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: Patrick Kelsey cc: freebsd-doc@freebsd.org Subject: Re: Improvement to pthread_getspecific(3) In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIIsWRmVeSWpSXmKPExsUixCmqrLtEMyrU4NZEdYtTZ7pYLY7ezXdg 8pjxaT5LAGMUl01Kak5mWWqRvl0CV8aWQ0+ZCrZxVlxeuImpgfE0excjJ4eEgInEnBVXWSFs MYkL99azgdhCAouZJB4uMehi5AKyNzJKXJ/wmhHCOcQk8erHWRYIp4FR4sqG6ywgLSwC2hJz Dx9kArHZBNQkHu9thhqrKLH51CRmEFtEQEPi9Y9ZYDazgLREw/rNQPUcHMICRhI7t2uDmJwC gRK7tkiDVPAKOEp8O3aWCeKgAIn9d66DTRQV0JFYvX8KC0SNoMTJmU9YICZqSSyfvo1lAqPQ LCSpWUhSCxiZVjHKpuRW6eYmZuYUpybrFicn5uWlFula6OVmluilppRuYgSFLLuL6g7GCYeU DjEKcDAq8fBOeBcRKsSaWFZcmXuIUZKDSUmUV041KlSILyk/pTIjsTgjvqg0J7X4EKMEB7OS CO8+RaAcb0piZVVqUT5MSpqDRUmcd9MPvhAhgfTEktTs1NSC1CKYrAwHh5IE7ywNoEbBotT0 1Iq0zJwShDQTByfIcB6g4VdBaniLCxJzizPTIfKnGBWlxHmXgCQEQBIZpXlwvbCU8opRHOgV YV5ukCoeYDqC634FNJgJaLDJtkiQwSWJCCmpBkb2DVP1mZm0s36tMXS8XaT9/nLs99/XLrlV /F+9w06MXd299b3l98f7V0Z4LC+Yzl/0t37huS+NhuLa2rvYj6Z94F0UV65eWjM99UwJX8xH Ya1pUpmidf2Ckop92/5Eml3jfNsa/NR8fudnmxftiSenz3q8fru8utjcQyolDP1tiQ3r1s2d K6fEUpyRaKjFXFScCADigcoLBAMAAA== X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2015 18:04:28 -0000 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