tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: Support -Ios='OpenBSD 5.1' to override uname(3)
Date: Fri, 25 May 2012 11:04:41 +0200	[thread overview]
Message-ID: <20120525090440.GA16868@britannica.bec.de> (raw)
In-Reply-To: <20120524234017.GA15573@iris.usta.de>

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?

Joerg
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2012-05-25  9:04 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 [this message]
2012-05-25 11:38   ` 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=20120525090440.GA16868@britannica.bec.de \
    --to=joerg@britannica.bec.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).