Github messages for mblaze
 help / color / mirror / Atom feed
From: Earnestly <Earnestly@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Confusing mshow behaviour with multipart/form-data
Date: Sun, 29 Aug 2021 21:36:25 +0200	[thread overview]
Message-ID: <20210829193625.57knQD8M_QFn1eTCIlMv0bFi_5XI7fi3xcw2JxXTJgE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-212@inbox.vuxu.org>

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

New comment by Earnestly on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/212#issuecomment-907854245

Comment:
I believe 0x0 should keep the content intact: https://0x0.st/-t59.txt

The paste should be of the working example, to replicate the issue you'll only have to add a newline above or below the existing content.

I don't think I'm being fooled although it is possible; I do try to check with either `cat -A` or `sed -n l` if in doubt (or throw `od` at it).

*Oh, I forget that github can do attachments but for now when I try it tells me: `Something went really wrong, and we can’t process that file.`.  This may be my fault though.*

  parent reply	other threads:[~2021-08-29 19:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 16:09 [ISSUE] " Earnestly
2021-08-29 18:07 ` leahneukirchen
2021-08-29 18:08 ` leahneukirchen
2021-08-29 19:18 ` Earnestly
2021-08-29 19:22 ` Earnestly
2021-08-29 19:36 ` Earnestly
2021-08-29 19:36 ` Earnestly [this message]
2021-08-29 19:37 ` Earnestly
2021-08-30 11:44 ` leahneukirchen
2021-08-30 11:46 ` leahneukirchen
2021-08-30 11:59 ` leahneukirchen
2021-08-30 16:13 ` leahneukirchen
2021-08-30 18:12 ` Earnestly
2021-08-30 18:19 ` leahneukirchen
2021-08-30 18:24 ` Earnestly
2021-08-30 18:24 ` [ISSUE] [CLOSED] " Earnestly

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=20210829193625.57knQD8M_QFn1eTCIlMv0bFi_5XI7fi3xcw2JxXTJgE@z \
    --to=earnestly@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).