Github messages for mblaze
 help / color / mirror / Atom feed
From: readmemyrights <>
Subject: [ISSUE] Needless awk evocations in mcom
Date: Sun, 09 Apr 2023 22:43:39 +0200	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

New issue by readmemyrights on mblaze repository

At multiple points in mcom
awk is invoked in the middle of a pipeline
like this:

awk '{ print }'

In the context of a pipeline
it's basically a no-op,
it prints out every line as read,
performing no additional processing.

I'll send a pull request shortly,
unless this command does something more that I just don't notice.

             reply	other threads:[~2023-04-09 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-09 20:43 readmemyrights [this message]
2023-04-10 10:16 ` leahneukirchen
2023-04-10 10:16 ` [ISSUE] [CLOSED] " leahneukirchen
2023-04-10 11:36 ` readmemyrights

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).