Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Nov 2020 17:26:11 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   =?UTF-8?B?W0J1ZyAyNTEwODFdIEdyZXAgQ3Jhc2hlcyB3aXRoIGJvdGggwqst?= =?UTF-8?B?LWFmdGVyLWNvbnRleHTCuyDCqy0tbWF4LWNvdW50wrsgU3dpdGNoZXMgYXJl?= =?UTF-8?B?IFVzZWQ=?=
Message-ID:  <bug-251081-227-AtqWRXxNlI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-251081-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-251081-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251081

--- Comment #4 from Igor Kolesnik <igorkolesnik@posteo.net> ---
(In reply to CrazyMihey from comment #3)

I'm not a FreeBSD developer.  The fix only exists as the proposed patch
attached to this ticket.  Actually, I don't know how it goes further from
here.

I searched for bugs related to grep

https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=3Dgrep&list_id=3D=
387710

and found that this bug already reported a quite time ago

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193835

Also, it seems that gnugrep is going to be dropped away in favor of bsdgrep.
And there is a port/package textproc/gnugrep which is free of this bug.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251081-227-AtqWRXxNlI>