From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: Fix typo in reading body from arg
Date: Tue, 18 Jun 2024 21:01:39 +0200 [thread overview]
Message-ID: <20240618190139.4B4DB23CF0@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-260@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
There's a closed pull request on the mblaze repository
Fix typo in reading body from arg
https://github.com/leahneukirchen/mblaze/pull/260
Description:
When given a body argument like this:
```
mcom foo@bar -body "this is my body"
```
the body isn't taken into account. This is because we try to `cat` from a file called "this is my body", instead of doing a process substitution for a file that fake-contains "this is my body". I believe it is a typo.
next prev parent reply other threads:[~2024-06-18 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 21:46 [PR PATCH] " rakoo
2024-06-18 19:01 ` leahneukirchen [this message]
2024-06-18 19:01 ` leahneukirchen
2024-06-18 19:51 ` rakoo
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=20240618190139.4B4DB23CF0@inbox.vuxu.org \
--to=leahneukirchen@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).