tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: "tech@mdocml.bsd.lv" <tech@mdocml.bsd.lv>
Subject: Re: PATCH: correct handling of literal tab characters
Date: Mon, 24 May 2010 23:22:50 +0200	[thread overview]
Message-ID: <4BFAEE2A.2050203@bsd.lv> (raw)
In-Reply-To: <20100524151808.GR13544@iris.usta.de>

> A test file is attached.
> 
> This patch is also available from
>   /usr/vhosts/mdocml.bsd.lv/patch/schwarze/05.tabbing.patch

This looks fine by me, although I'd like a bit more in-code 
documentation in the critical sections.  Note that I didn't test the 
patch, as it didn't apply.  When you get it checked in, respond to this 
and I'll run it through the usual battery of tests to make sure nothing 
in one of the million manuals I have around pukes.

Commit it!
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2010-05-24 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 15:18 Ingo Schwarze
2010-05-24 21:22 ` Kristaps Dzonsons [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=4BFAEE2A.2050203@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).