From: readmemyrights <readmemyrights@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Needless awk evocations in mcom
Date: Mon, 10 Apr 2023 13:36:10 +0200 [thread overview]
Message-ID: <20230410113610.2cOB1iSqlXhPHdU8G9FvEqNvsG3sqMOzw3Ri0z6Hj5A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-238@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
New comment by readmemyrights on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/238#issuecomment-1501719033
Comment:
Thanks for the quick reply, it certainly does make sense
prev parent reply other threads:[~2023-04-10 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 20:43 [ISSUE] " readmemyrights
2023-04-10 10:16 ` leahneukirchen
2023-04-10 10:16 ` [ISSUE] [CLOSED] " leahneukirchen
2023-04-10 11:36 ` readmemyrights [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=20230410113610.2cOB1iSqlXhPHdU8G9FvEqNvsG3sqMOzw3Ri0z6Hj5A@z \
--to=readmemyrights@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).