From owner-freebsd-doc@FreeBSD.ORG Fri Apr 25 14:00:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5AE3EFF0 for ; Fri, 25 Apr 2014 14:00:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 477BC173A for ; Fri, 25 Apr 2014 14:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3PE01pA026799 for ; Fri, 25 Apr 2014 14:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3PE01fH026798; Fri, 25 Apr 2014 14:00:01 GMT (envelope-from gnats) Date: Fri, 25 Apr 2014 14:00:01 GMT Message-Id: <201404251400.s3PE01fH026798@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: "Michael Kerrisk (man-pages)" Subject: Re: docs/188786: Bug in inet(3) man page (inet_aton()) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: "Michael Kerrisk \(man-pages\)" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2014 14:00:01 -0000 The following reply was made to PR docs/188786; it has been noted by GNATS. From: "Michael Kerrisk (man-pages)" To: Mark Linimon Cc: freebsd-gnats-submit@freebsd.org Subject: Re: docs/188786: Bug in inet(3) man page (inet_aton()) Date: Fri, 25 Apr 2014 15:52:46 +0200 Thanks for the info, Mark. On Sat, Apr 19, 2014 at 2:54 PM, Mark Linimon wrote: > On Sat, Apr 19, 2014 at 07:06:48AM +0000, Michael Kerrisk wrote: >> I see the same text in the OpenBSD page, and also the NetBSD page. >> How does this work -- should I submit bugs for each of those systems, >> or do communicate such problems to one another? > > Short answer: we do't automatically sync with one another. > > Longer answer: it would take some investigation to find out if one or > the other of the 3 has a "canonical" set of manpages that the others > have copied. So, the best way is to open a PR for each. > > Thanks. > > mcl -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/