From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scc-mailout.scc.kit.edu (scc-mailout.scc.kit.edu [129.13.185.201]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p9GGg34I029740 for ; Sun, 16 Oct 2011 12:42:04 -0400 (EDT) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by scc-mailout-01.scc.kit.edu with esmtp (Exim 4.72 #1) id 1RFTml-00051v-8Y; Sun, 16 Oct 2011 18:42:03 +0200 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RFTml-0002bA-7u; Sun, 16 Oct 2011 18:42:03 +0200 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RFTml-0001uj-6S; Sun, 16 Oct 2011 18:42:03 +0200 Received: from schwarze by usta.de with local (Exim 4.72) (envelope-from ) id 1RFTml-0002Ky-5P; Sun, 16 Oct 2011 18:42:03 +0200 Date: Sun, 16 Oct 2011 18:42:03 +0200 From: Ingo Schwarze To: tech@mdocml.bsd.lv Cc: Jason McIntyre Subject: Re: fill gaps in arch.in and lib.in Message-ID: <20111016164203.GH27850@iris.usta.de> References: <20111016150630.GE27850@iris.usta.de> <20111016155419.GC8820@harkle.home.gateway> <20111016161005.GG27850@iris.usta.de> <4E9B02FC.5080504@bsd.lv> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E9B02FC.5080504@bsd.lv> User-Agent: Mutt/1.5.21 (2010-09-15) Hi Kristaps, Kristaps Dzonsons wrote on Sun, Oct 16, 2011 at 06:14:52PM +0200: > As for the manual page, perhaps we can narrow it down to the "big > ones" and simply mention that most others modern platforms are > supported? The big ones being i386, amd64, sparc, > sparc64---whatever. I agree that a Big List is a bad idea, as well > as listing nothing. This would strike a nice balance. Maybe even simpler: In the individual operating systems, let's keep everything as it is. In the generic bsd.lv version, let's just put something like: The list of supported architectures varies by operating system. For the full list of all architectures recognized by mandoc(1), see the file arch.in in the source distribution. Note that mandoc(1) can format manuals for all architectures and operating systems on any platform. Yours, Ingo -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv