From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chroot-grep: patch out problematic warnings in egrep and fgrep.
Date: Thu, 12 Jan 2023 19:30:05 +0100 [thread overview]
Message-ID: <20230112183005.FWB1SWVjA1ZNy5tGKu3y4xtrbljVTo0HzBnrxyZTwdM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41593@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/41593#issuecomment-1380834924
Comment:
I am still against this even though this was merged, the grep package regular users get has this patched out and we are able to fix this in packaging and send PRs upstream. This is an upstream decision and packages that use e/fgrep and this causes an issue should be fixed instead.
prev parent reply other threads:[~2023-01-12 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 7:27 [PR PATCH] " icp1994
2023-01-12 7:28 ` paper42
2023-01-12 7:32 ` icp1994
2023-01-12 17:15 ` [PR PATCH] [Merged]: " Vaelatern
2023-01-12 18:30 ` paper42 [this message]
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=20230112183005.FWB1SWVjA1ZNy5tGKu3y4xtrbljVTo0HzBnrxyZTwdM@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).