From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: remove "please" from manual page; patch from jsg@, ok jmc@
Date: Tue, 8 Feb 2022 13:28:15 -0500 (EST) [thread overview]
Message-ID: <33642dabb495156e@mandoc.bsd.lv> (raw)
Log Message:
-----------
remove "please" from manual page;
patch from jsg@, ok jmc@ sthen@ millert@
Modified Files:
--------------
mandoc:
mandoc.1
Revision Data
-------------
Index: mandoc.1
===================================================================
RCS file: /home/cvs/mandoc/mandoc/mandoc.1,v
retrieving revision 1.253
retrieving revision 1.254
diff -Lmandoc.1 -Lmandoc.1 -u -p -r1.253 -r1.254
--- mandoc.1
+++ mandoc.1
@@ -835,7 +835,7 @@ message levels, the
.Cm style
level tries to reduce the probability that issues go unnoticed,
so it may occasionally issue bogus suggestions.
-Please use your good judgement to decide whether any particular
+Use your judgement to decide whether any particular
.Cm style
suggestion really justifies a change to the input file.
.It Cm base
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2022-02-08 18:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=33642dabb495156e@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
--subject='Re: mandoc: remove "please" from manual page; patch from jsg@, ok jmc@' \
/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).