X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org CB3443857C44
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1679800079;
	bh=n/gewK981BdDCsrYUhAOwDfLDR2i4C6m5XgfG12CDM4=;
	h=To:Date:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:
	List-Help:List-Subscribe:From:Reply-To:Cc:From;
	b=YkgsPhSIzGkLcwduT7WKvzvmb7kH9eRc+JFrzUkukZQQi+7h072h+ql78suoofxQd
	5m3attziMC6KVbwSYo2G4IQ1/hozSVp2RtmFxMZR0KSJwUbQ0JxIMtRqC/2mRsDRxh
	D1VY4q+gIuvA6D6a3i84wB/vA0XxEq4p/4bcGSP4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 5C625385841A
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 276853858033
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org EA039385B518
X-Authority-Analysis:	v=2.4 cv=VbHkgXl9 c=1 sm=1 tr=0 ts=641fb6d1
	a=DxHlV3/gbUaP7LOF0QAmaA==:117 a=DxHlV3/gbUaP7LOF0QAmaA==:17 a=mDV3o1hIAAAA:8
	a=vJZTLffKzVtHjoEVQeEA:9 a=_FVE-zBwftR9WsbkzFJk:22
To:	cygwin AT cygwin DOT com
Date:	Sat, 25 Mar 2023 21:06:05 -0600
Message-Id:	<announce.20230325210605.15868-1-Brian.Inglis@Shaw.ca>
Subject:	[ANNOUNCEMENT] Upgraded: grep 3.10
X-CMAE-Envelope:	MS4xfNspPkiI9WSMT2xPhFjvpTpgaeK8jRXskiukwVCOMvvo4OEOrrhHRQES0S5zjHOYnMDTeROgpb5C3im1Ry+tgtiBpfcmAdfqBe18dBDT9bJvky1Hludv
	yoQTdUXwVlZyzC1zJyUJqyLPbY9rohWJkS82knBCE5MCbnFDH3VTDIbzNaSbvETKtLUs/lXxXpCCLbQFFgn1VEqlXleuEUpCUBo=
X-Spam-Status:	No, score=-1.3 required=5.0 tests=BAYES_00, BODY_8BITS,
	DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT,
	KAM_SHORT, PP_MIME_FAKE_ASCII_TEXT, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin-announce AT cygwin DOT com
X-Mailman-Version:	2.1.29
X-Mailer:	Perl5 Mail::Internet v2.20
X-BeenThere:	cygwin AT cygwin DOT com
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Cygwin grep Co-Maintainer via Cygwin-announce via Cygwin
	<cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Cygwin grep Co-Maintainer via Cygwin-announce <cygwin-announce AT cygwin DOT com>,
	Cygwin grep Co-Maintainer <Brian DOT Inglis AT Shaw DOT ca>
MIME-Version:	1.0
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Note-from-DJ:	This may be spam

--===============3296406093906074051==
Content-Type: text/plain

The following package has been upgraded in the Cygwin distribution:

* grep	3.10

GNU grep searches one or more input files for lines containing a match
to a specified pattern. By default, grep outputs the matching lines. The
GNU implementation includes several useful extensions over POSIX.

The previous release stated that egrep and fgrep are deprecated
obsolescent commands, will be dropped in future, and from this release
until then, every use will show a stderr warning message, reminding you
how to change your commands and scripts:

	$ egrep ...
	egrep: warning: egrep is obsolescent; using grep -E
	...
	$ fgrep ...
	fgrep: warning: fgrep is obsolescent; using grep -F
	...

Cygwin releases will suppress the egrep and fgrep warning messages, but
developers and maintainers should rigorously remove all such usages from
their practices and scripts, as those commands could be dropped, or any
warning messages could be treated as fatal errors, in future.

Other invalid usages documented previously also now generate stderr
warning or error messages e.g.

	grep: warning: * at start of expression
	grep: warning: ? at start of expression
	grep: warning: + at start of expression
	grep: warning: {...} at start of expression
	grep: warning: stray \ before <CHAR>
	grep: warning: stray \ before unprintable character
	grep: warning: stray \ before white space

For more information see the project home pages:

	https://www.gnu.org/software/grep/
	https://sv.gnu.org/projects/grep/

For changes since the previous Cygwin release please see below or read
/usr/share/doc/grep/NEWS after installation; for complete details see:

	/usr/share/doc/grep/ChangeLog
	https://git.sv.gnu.org/gitweb/?p=grep.git;a=log;h=refs/tags/v3.9


Noteworthy changes in release 3.10	2023-03-22

* Bug fixes

  With -P, \d now matches only ASCII digits, regardless of PCRE
  options/modes. The changes in grep-3.9 to make \b and \w work
  properly had the undesirable side effect of making \d also match
  e.g., the Arabic digits: ٠١٢٣٤٥٦٧٨٩.  With grep-3.9, -P '\d+'
  would match that ten-digit (20-byte) string. Now, to match such
  a digit, you would use \p{Nd}. Similarly, \D is now mapped to [^0-9].
  [bug introduced in grep 3.9]


--===============3296406093906074051==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

--===============3296406093906074051==--

- Raw text -