From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: Support -Ios='OpenBSD 5.1' to override uname(3)
Date: Fri, 25 May 2012 13:38:57 +0200 [thread overview]
Message-ID: <20120525113857.GA10563@iris.usta.de> (raw)
In-Reply-To: <20120525090440.GA16868@britannica.bec.de>
Hi Joerg,
Joerg Sonnenberger wrote on Fri, May 25, 2012 at 11:04:41AM +0200:
> On Fri, May 25, 2012 at 01:40:17AM +0200, Ingo Schwarze wrote:
>> Bob Beck definitely wanted this for man.cgi, so i have put it into
>> OpenBSD. I'd like to push it upstream, as well; i think the problem
>> occurs in general as soon as you want to serve manuals from multiple
>> operating systems or releases from the same server.
> I don't have a problem with the feature in general, but why -I?
We have -O for output options (i.e. options bound to specific output
formats and used while generating the output), so by analogy,
this is -I for an input option (i.e. an option bound to the specific
input format, mdoc(7), and used while parsing the input file).
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2012-05-25 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 23:40 Ingo Schwarze
2012-05-25 9:04 ` Joerg Sonnenberger
2012-05-25 11:38 ` 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=20120525113857.GA10563@iris.usta.de \
--to=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).