From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: PATCH: mdoc_ptext rewrite
Date: Mon, 24 May 2010 16:27:54 +0200 [thread overview]
Message-ID: <20100524142754.GQ13544@iris.usta.de> (raw)
In-Reply-To: <4BFA8ABC.90009@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Mon, May 24, 2010 at 04:18:36PM +0200:
> >Kristaps Dzonsons wrote on Mon, May 24, 2010 at 03:59:49PM +0200:
>>> Replying to myself... can you pop in some regression tests that test
>>> against free-form text tab/space inclusions?
>> After syncing, i need to do a two-way sync of regression tests
>> anyway. Yes, certainly it is possible to test for this.
>>> Also, is this behaviour different in -man?
>> Frankly, i have no idea.
> Let's just copy over the free-form text tests
cp: No such file or directory, yet. :)
> to have a -man header and catch fallout from there.
Apart form that minor issue, sure.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-05-24 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 13:19 Ingo Schwarze
2010-05-24 13:38 ` Kristaps Dzonsons
2010-05-24 13:59 ` Kristaps Dzonsons
2010-05-24 14:12 ` Ingo Schwarze
2010-05-24 14:18 ` Kristaps Dzonsons
2010-05-24 14:27 ` 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=20100524142754.GQ13544@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).