discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jason McIntyre <jmc@kerhand.co.uk>
To: Thomas Klausner <wiz@NetBSD.org>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mdoc.7: tweak skeleton file
Date: Sun, 29 Aug 2010 12:32:46 +0059	[thread overview]
Message-ID: <20100829113310.GB10462@bramka.kerhand.co.uk> (raw)
In-Reply-To: <20100829105032.GD12803@danbala.tuwien.ac.at>

On Sun, Aug 29, 2010 at 12:50:32PM +0200, Thomas Klausner wrote:
> 
> Well, here's the correction. That's the order currently checked by
> pkgsrc/textproc/mdoclint/files/mdoclint:
>         my @sections = (
>                 "NAME",
>                 NETBSD ? "LIBRARY" : undef,
>                 "SYNOPSIS",
>                 "DESCRIPTION",
>                 "IMPLEMENTATION NOTES",
>                 "RETURN VALUES",
>                 "ENVIRONMENT",
>                 "FILES",
>                 "EXIT STATUS",
>                 "EXAMPLES",
>                 "DIAGNOSTICS",
>                 "COMPATIBILITY",
>                 "ERRORS",
>                 "SEE ALSO",
>                 "STANDARDS",
>                 "HISTORY",
>                 "AUTHORS",
>                 "CAVEATS",
>                 "BUGS",
>                 NETBSD ? "SECURITY CONSIDERATIONS" : undef
>         );
> 
> (Btw, pages actually using IMPLEMENTATION NOTES are e.g. bdes(1),
> which compares to Sun's implementation; or stdio(3), which mentions
> which functions are macros or support locking.)
> 
> Cheers,
>  Thomas

grr, we were meant to keep these files in sync. can you please mail me
when you make changes to this?

anyway, i guess i can update ours. have netbsd actually moved pages into
this order then?

i'll send you a diff to mdoclint to check it's ok later. for now,
there's a grand prix on!

jmc
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-08-29 11:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 18:24 Jason McIntyre
2010-08-28 21:12 ` Kristaps Dzonsons
2010-08-28 22:01   ` Jason McIntyre
2010-08-28 22:08     ` Kristaps Dzonsons
2010-08-28 22:18       ` Jason McIntyre
2010-08-28 22:38       ` Jason McIntyre
2010-08-28 23:14         ` Kristaps Dzonsons
2010-08-29  9:10           ` Jason McIntyre
2010-08-29 10:50             ` Thomas Klausner
2010-08-29 11:33               ` Jason McIntyre [this message]
2010-08-29 12:09                 ` Thomas Klausner
2010-08-29 16:17                   ` Jason McIntyre
2010-08-29 17:26                     ` Kristaps Dzonsons
2010-08-29 18:06                       ` Ulrich Spörlein
2010-08-29 18:28                         ` Jason McIntyre
2010-08-29 20:57                           ` Thomas Klausner
2010-08-30  6:43                             ` Jason McIntyre
2010-08-30  9:01                               ` Thomas Klausner
2010-08-30 12:16                                 ` Jason McIntyre
2010-08-30 12:21                                   ` Thomas Klausner
2010-08-30 12:29                                     ` Kristaps Dzonsons
2010-08-31 17:54                                   ` Jason McIntyre

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=20100829113310.GB10462@bramka.kerhand.co.uk \
    --to=jmc@kerhand.co.uk \
    --cc=discuss@mdocml.bsd.lv \
    --cc=wiz@NetBSD.org \
    /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).