discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: paul@apatience.com
Cc: discuss@mandoc.bsd.lv
Subject: Re: Spurious space in demandoc.1
Date: Sun, 20 Mar 2022 17:05:25 +0100	[thread overview]
Message-ID: <YjdQxY5m7nVvwepn@asta-kit.de> (raw)
In-Reply-To: <YjdPn3zr1yrOiitu@asta-kit.de>

Ingo Schwarze wrote on Sun, Mar 20, 2022 at 05:00:31PM +0100:

> However, the whole sentence is misplaced, meaningless, and confusing
> in this manual page, so i just deleted the whole line outright,
> see the committed patch below.

Oops, sorry, i accidentally omitted the commit message in
this mailing list post, so here it is.


Log Message:
-----------
The demandoc(1) program neither reads nor writes any databases, so
delete a sentence taking about databases.  Having that sentence in
the first place probably was a copy-and-paste mistake when adopting
some text from the makewhatis(8) manual page.

Triggered by a smaller patch sent to discuss@
by Paul A. Patience <paul at apatience dot com>.


> Index: demandoc.1
> ===================================================================
> RCS file: /home/cvs/mandoc/mandoc/demandoc.1,v
> retrieving revision 1.8
> diff -u -r1.8 demandoc.1
> --- demandoc.1	12 Sep 2014 00:10:26 -0000	1.8
> +++ demandoc.1	20 Mar 2022 15:36:09 -0000
> @@ -80,7 +80,6 @@
>  Such errors cause
>  .Nm
>  to exit at once, possibly in the middle of parsing or formatting a file.
> -The output databases are corrupt and should be removed .
>  .El
>  .Sh EXAMPLES
>  The traditional usage of
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


      reply	other threads:[~2022-03-20 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13  1:20 Paul A. Patience
2022-03-20 16:00 ` Ingo Schwarze
2022-03-20 16:05   ` 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=YjdQxY5m7nVvwepn@asta-kit.de \
    --to=schwarze@usta.de \
    --cc=discuss@mandoc.bsd.lv \
    --cc=paul@apatience.com \
    --subject='Re: Spurious space in demandoc.1' \
    /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

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).