From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: grep: update to 3.10
Date: Fri, 31 Mar 2023 13:29:21 +0200 [thread overview]
Message-ID: <20230331112921.sa0jRf4H7DzR3sfv07FdK6x-pImfKn-udpiaGGILuP8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43139@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/43139#issuecomment-1491778089
Comment:
> I took the trouble of making a pull request to update the template of the grep package, the package that you usually maintain.
I don't know if this passive aggressive tone was intentional or not, please try to pay more attention to what you are writing and how it could be interpreted.
next prev parent reply other threads:[~2023-03-31 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 10:51 [PR PATCH] " tuxliban
2023-03-31 11:04 ` paper42
2023-03-31 11:04 ` [PR PATCH] [Closed]: " paper42
2023-03-31 11:29 ` paper42 [this message]
2023-03-31 17:05 ` tuxliban
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=20230331112921.sa0jRf4H7DzR3sfv07FdK6x-pImfKn-udpiaGGILuP8@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).