From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mandocdb(8) fixes
Date: Fri, 2 Dec 2011 00:24:46 +0100 [thread overview]
Message-ID: <20111201232446.GD25169@iris.usta.de> (raw)
In-Reply-To: <4ED698E9.6090002@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Wed, Nov 30, 2011 at 09:58:17PM +0100:
> While endian-neutralising mandocdb(8), I noticed that it broke with
> the last series of commits: the manual type (mdoc, man, cat) wasn't
> accounted for when pruning the database.
Oops, yaya, sorry, i broke that.
I missed that function.
> The enclosed patch takes account for this. It also adds some
> in-line documentation. It also removes the "verb > 1" parts, which
> I find a little unnecessary (they can be added back in).
Looks good and merged to OpenBSD.
Thanks,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-12-01 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 20:58 Kristaps Dzonsons
2011-11-30 21:09 ` Kristaps Dzonsons
2011-12-01 23:24 ` 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=20111201232446.GD25169@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).