From: Anachron <Anachron@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Attachment not found
Date: Fri, 06 Nov 2020 20:20:57 +0100 [thread overview]
Message-ID: <20201106192057.zV0UHVZbqXibO0uGisd5oGgZz3COkgL80zKJCFZ9a70@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-191@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
New comment by Anachron on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/191#issuecomment-723255447
Comment:
Yep, I believe this should be a trivial fix? It not I can write a simple wrapper running "test -f".
next prev parent reply other threads:[~2020-11-06 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 10:30 [ISSUE] " Anachron
2020-11-04 11:18 ` leahneukirchen
2020-11-06 19:20 ` Anachron [this message]
2020-11-08 14:10 ` [ISSUE] [CLOSED] " leahneukirchen
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=20201106192057.zV0UHVZbqXibO0uGisd5oGgZz3COkgL80zKJCFZ9a70@z \
--to=anachron@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).