From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: do not skip manuals shared across architectures
Date: Wed, 28 Dec 2011 01:37:47 +0100 [thread overview]
Message-ID: <20111228003747.GA30880@iris.usta.de> (raw)
In-Reply-To: <4EFA5C13.6010504@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Wed, Dec 28, 2011 at 02:00:19AM +0200:
> On 26/12/2011 13:48, Ingo Schwarze wrote:
>> You want this on bsd.lv, too?
> Yes, please commit.
Done, thanks.
> Can you also document these checks in mandocdb(8) so people can
> know more or less what `-t' is checking for?
In the long run, yes, i think that makes sense.
Right now, these checks are still too volatile.
I'm not looking forward to rewriting the docs
multiple times.
I think the right time will be after the first round of dealing
with fallout from the base builds has been completed - this commit
was just the first of this round, several more are required for
polishing - *and* after a careful comparison against espie@'s
OpenBSD::Makewhatis modules has been completed. At that point,
i hope for the tests to become more or less stable.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-12-28 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 11:48 Ingo Schwarze
2011-12-28 0:00 ` Kristaps Dzonsons
2011-12-28 0:37 ` 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=20111228003747.GA30880@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).