From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: mdoc section ordering
Date: Tue, 11 May 2010 21:58:56 +0059 [thread overview]
Message-ID: <20100511205920.GC24992@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4BE9B98D.3060706@bsd.lv>
On Tue, May 11, 2010 at 10:09:49PM +0200, Kristaps Dzonsons wrote:
>
> Jason, in my opinion, COMPATIBILITY and STANDARDS shouldn't be merged in
> all cases. Take mdocml's man.7 and mdoc.7, for example: the
> COMPATIBILITY section is used to enumerate the differences between
> troffs and mandoc. Since -man, -mdoc, etc. aren't standards, where else
> would this go?
>
a separate section sometimes makes sense, yes. but for the general case,
we found it didn;t warrant the need for an "official" section.
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-05-11 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 11:52 Ulrich Spörlein
2010-05-11 13:45 ` Jason McIntyre
2010-05-11 14:57 ` Ulrich Spörlein
2010-05-11 15:43 ` Jason McIntyre
2010-05-11 16:23 ` Ulrich Spörlein
2010-05-11 20:09 ` Kristaps Dzonsons
2010-05-11 20:27 ` Ulrich Spörlein
2010-05-11 20:59 ` Jason McIntyre [this message]
2010-05-12 12:50 ` Kristaps Dzonsons
2010-05-13 22:23 ` Thomas Klausner
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=20100511205920.GC24992@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@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).