Subject: bug#19719: closed (Re: bug#19719: grep(1) man page for GNU grep 2.16 shold have PCRE but has PRCE)

From: [email-masked] (GNU bug Tracking System)
Date: Tue, 17 Feb 2015 03:44:02 +0000

Your bug report

#19719: grep(1) man page for GNU grep 2.16 shold have PCRE but has PRCE 

which was filed against the grep package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
19719: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19719
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#19719: grep(1) man page for GNU grep 2.16 shold have PCRE but has PRCE
From: Jim Meyering <[email-masked]>
To: Philip Muench <[email-masked]>
Cc: [email-masked]
Date: Mon, 16 Feb 2015 19:43:13 -0800
List-Id: <debbugs-submit.debbugs.gnu.org>

On Wed, Jan 28, 2015 at 1:12 PM, Philip Muench
<[email-masked]> wrote:
> There is one instance of PRCE. It should be PCRE.  That would help the reader seeking PCRE.

Thank you for reporting that.
However, there has never been an occurrence of the string PRCE in the
upstream sources, so this is probably due to a distribution-specific patch
in use on your system.  Also note that there have been significant fixes
and improvements since grep-2.16.  The latest is grep-2.21.

Subject: grep(1) man page for GNU grep 2.16 shold have PCRE but has PRCE
From: Philip Muench <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Wed, 28 Jan 2015 21:12:19 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

There is one instance of PRCE. It should be PCRE.  That would help the reader seeking PCRE.
<http://www.fibermountain.com>
Philip Muench

[email-masked]

700 West Johnson Avenue
Cheshire, CT06410
www.fibermountain.com        P. (203) 806-4040
C.
F. (845) 358-7882
Disclaimer: The information contained in this communication is confidential, may be privileged and is intended for the exclusive use of the above named addressee(s). If you are not the intended recipient(s), you are expressly prohibited from copying, distributing, disseminating, or in any other way using any information contained within this communication. If you have received this communication in error, please contact the sender by telephone or by response via mail. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on this message, as well as any attachments. We cannot accept liability for any loss or damage caused by software viruses.