From owner-freebsd-doc@FreeBSD.ORG Sun Jan 4 18:23:32 2009 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4764106564A; Sun, 4 Jan 2009 18:23:32 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 7FFC78FC0C; Sun, 4 Jan 2009 18:23:32 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.2/8.14.2) with ESMTP id n04INK1F057951; Mon, 5 Jan 2009 03:23:31 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id n04IN8LJ063610; Mon, 5 Jan 2009 03:23:10 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 05 Jan 2009 03:22:11 +0900 (JST) Message-Id: <20090105.032211.33865530.hrs@allbsd.org> To: danger@FreeBSD.org From: Hiroki Sato In-Reply-To: <1289663263.20090104185721@rulez.sk> References: <287359450.20090104174842@rulez.sk> <20090105.025058.119952164.hrs@allbsd.org> <1289663263.20090104185721@rulez.sk> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.2 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Jan__5_03_22_11_2009_552)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Mon, 05 Jan 2009 03:23:31 +0900 (JST) Cc: doc@FreeBSD.org, brueffer@FreeBSD.org Subject: Re: svn commit: r186737 - head/sbin/geom/class/virstor X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 18:23:33 -0000 ----Security_Multipart(Mon_Jan__5_03_22_11_2009_552)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Daniel Gerzo wrote in <1289663263.20090104185721@rulez.sk>: da> Hello Hiroki, da> da> Sunday, January 4, 2009, 6:50:58 PM, you wrote: da> da> > Daniel Gerzo wrote da> > in <287359450.20090104174842@rulez.sk>: da> da> da>> Hello Christian, da> da>> da> da>> Sunday, January 4, 2009, 4:58:32 PM, you wrote: da> da>> da> da>> > While using .Ex is good, collapsing EXIT STATUS into DIAGNOSTICS is not. da> da>> > EXIT STATUS is a standard section in our manpages and it's orthogonal to da> da>> > DIAGNOSTICS. da> da>> da> da>> I am fine to revert this part, however I have trimmed this section da> da>> just because I didn't see it listed in the PAGE STRUCTURE DOMAIN da> da>> section of the mdoc(7) manual page. da> da>> da> da>> Interestingly, it lists the DIAGNOSTICS section and explicitly da> da>> says that .Ex macro should be used there. da> da> > Is using .Ex macro really correct?. When geom(1) fails the exit da> > status will be 1, not >0. While many commands whose manual page says da> > so return 1 on an error actually (especially when it is in POSIX), da> > the two are not the same at least. da> da> I thought that 1 > 0 ... (?) I mean I am wondering if rewriting "1" with ">0" is reasonable or not. "1>0" is always true, but "1" is not equal to ">0". Some other manual pages have the description "1 on error.". If we have a consensus on that this rewriting is reasonable, we should also rewrite them in consistency. -- | Hiroki SATO ----Security_Multipart(Mon_Jan__5_03_22_11_2009_552)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklg/lQACgkQTyzT2CeTzy1kqQCZAZTyiCRUjtxLKYQomHxHMfPI 5A4An3tcnp9SFvvt6X67rMjqW22DjB4P =JxDs -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Jan__5_03_22_11_2009_552)----