Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Mar 2023 18:54:26 -0500
From:      Ed Maste <emaste@freebsd.org>
To:        Warner Losh <imp@bsdimp.com>
Cc:        Kyle Evans <kevans@freebsd.org>, src-committers@freebsd.org,  dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org,  Steffen Nurpmeso <steffen@sdaoden.eu>
Subject:   Re: git: ceb5f28ba5fc - main - freebsd-update: re-edit files if merge conflict markers remain
Message-ID:  <CAPyFy2C4VKtaiijvpuNLvYwUc8kUVGRtiFzcredLrM8rUaDrmw@mail.gmail.com>
In-Reply-To: <CANCZdfpW0iv_sO5ae8qUED-FWY-Lt0WM5_DAtouzS_-n-Cun_Q@mail.gmail.com>
References:  <202303020121.3221LWHh070834@gitrepo.freebsd.org> <20230302192204.YPJ7f%steffen@sdaoden.eu> <CACNAnaGpBNEWbmrkFQ1zpYn%2BfxvyduPoN2ymm7H56qGi3pHTCQ@mail.gmail.com> <CANCZdfpW0iv_sO5ae8qUED-FWY-Lt0WM5_DAtouzS_-n-Cun_Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Mar 2023 at 15:37, Warner Losh <imp@bsdimp.com> wrote:
>
> I doubt egrep will ever be deprecated. Too many scripts depend on it.
> And fixing this one is a drop in the bucket. I personally think the warning
> from gnu-grep is bananas...

Agreed on both points.

In the man page we have:
      -E, --extended-regexp
             Interpret pattern as an extended regular expression (i.e., force
             grep to behave as egrep).

That said, it's conceivable that this could end up invoking GNU egrep
and thus emit a warning. It doesn't hurt to use grep -E instead.



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