Github messages for mblaze
 help / color / mirror / Atom feed
From: codesoap <>
Subject: Re: mcom: do not match shebang in needs_multipart()
Date: Mon, 04 Jan 2021 19:14:30 +0100	[thread overview]
Message-ID: <20210104181430.8xidUae0ZdmSZ3OxLnHph4WPC40-DQtSjj3tCIOdAGg@z> (raw)
In-Reply-To: <>

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

New comment by codesoap on mblaze repository

> Ok, but running mmime does no harm here right?

Running mmime doesn't do much harm, but it changes the message encoding from `text/plain` to `multipart/mixed`.

> I'd probably use a regexp that matches what we do in mmime.c

OK, thanks for the hint. I'll take a look.

  parent reply	other threads:[~2021-01-04 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 17:59 [PR PATCH] " codesoap
2021-01-04 18:04 ` leahneukirchen
2021-01-04 18:05 ` leahneukirchen
2021-01-04 18:14 ` codesoap [this message]
2021-01-04 18:15 ` leahneukirchen
2021-01-04 18:16 ` leahneukirchen
2021-01-04 18:16 ` leahneukirchen
2021-01-04 18:19 ` codesoap
2021-01-04 18:21 ` [PR PATCH] [Updated] " codesoap
2021-01-04 18:22 ` codesoap
2021-01-04 18:27 ` [PR PATCH] [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:

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

  git send-email \
    --in-reply-to=20210104181430.8xidUae0ZdmSZ3OxLnHph4WPC40-DQtSjj3tCIOdAGg@z \ \ \

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