From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>, Jason McIntyre <jmc@cava.myzen.co.uk>
Subject: Re: fill gaps in arch.in and lib.in
Date: Mon, 24 Oct 2011 18:30:12 +0200 [thread overview]
Message-ID: <4EA59294.3020900@bsd.lv> (raw)
In-Reply-To: <20111016164203.GH27850@iris.usta.de>
On 10/16/11 18:42, Ingo Schwarze wrote:
> 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.
Ingo,
I think this is fine, considering the options. Of course a remaining
option is to make a mandoc_arch(7) manual, but then we'd need
mandoc_lib(7) too... but that's just messy.
I think a similar note should be put into the `Lb' documentation in
referring to libraries in lib.in, too, as it's not a fixed set.
Thoughts?
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-10-24 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 15:06 Ingo Schwarze
[not found] ` <20111016155419.GC8820@harkle.home.gateway>
2011-10-16 16:10 ` Ingo Schwarze
2011-10-16 16:14 ` Kristaps Dzonsons
2011-10-16 16:42 ` Ingo Schwarze
2011-10-24 16:30 ` Kristaps Dzonsons [this message]
2011-10-24 22:25 ` Ingo Schwarze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA59294.3020900@bsd.lv \
--to=kristaps@bsd.lv \
--cc=jmc@cava.myzen.co.uk \
--cc=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).