discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: jmc@openbsd.org
Cc: discuss@mdocml.bsd.lv
Subject: Re: Where to put mandoc roff documentation?
Date: Sat, 27 Nov 2010 22:46:31 +0100	[thread overview]
Message-ID: <20101127214631.GC27534@iris.usta.de> (raw)
In-Reply-To: <20101127211832.GA27550@kerhand.co.uk>

Hi Jason,

Jason McIntyre wrote on Sat, Nov 27, 2010 at 09:18:08PM +0000:

> it sounds like one page is a good idea for this stuff - roff, troff,
> whatever. i wouldn;t worry about squashing a groff page - the port could
> be tweaked to install under a different name.
> 
> so i;d say yes, stick 1, 2, and 3 in a roff page.

Good, so i shall soon move roff.7 to share/man/man7 and start
polishing it such that we can install it once we feel it is ripe.
I assume Kristaps won't object to keeping the name either,
because he was the one initially choosing it.  :)

Once we will be installing it, we can then start moving class 1
stuff there.

> if there's stuff more suited to mdoc (or repeated), i'd leave it in mdoc
> and have roff point to it (i.e. point 4).

Oh, yes, pointing that way didn't occur to me yet, but may also be
an option for some cases.

> we don;t have to worry too much - if it evolves into something else, we
> can change it in the future.

Good, so let's see where we get.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2010-11-27 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 18:45 Ingo Schwarze
2010-11-27 21:18 ` Jason McIntyre
2010-11-27 21:46   ` Ingo Schwarze [this message]

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=20101127214631.GC27534@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=jmc@openbsd.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).