From: David Marchand <david.marchand@redhat.com>
To: Ben Woodard <woodard@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
libabigail@sourceware.org,
vsoch <vsoch@users.noreply.github.com>
Subject: Re: [PATCH] Add github actions to support workflows
Date: Tue, 3 May 2022 12:52:54 +0200 [thread overview]
Message-ID: <CAJFAV8xkXfPVhoKj6XbGhi9PAMtmAY0nSBtOxDbGhpVXVuOMLQ@mail.gmail.com> (raw)
In-Reply-To: <3DD6B8FC-EEA1-4ABB-81AE-8D28189837A8@redhat.com>
On Tue, May 3, 2022 at 2:18 AM Ben Woodard via Libabigail
<libabigail@sourceware.org> wrote:
>
>
> > On Apr 30, 2022, at 1:08 PM, Mark Wielaard <mark@klomp.org> wrote:
> >
> > Hi Ben,
> >
> > On Fri, Apr 22, 2022 at 09:17:16AM -0700, Ben Woodard via Libabigail wrote:
> > [ ... application/octet-stream ...]
> >
> > Aha, there are those scripts and container files. But sending the
> > patches as application/octet-stream causes them to be hidden in my mua
> > (mutt).
> >
>
> Yeah I talked to Frank about that and he thinks that was a bug in Fedora 36 that day and it mime-ified the output of git send-email. I got the impression that he had seen it somewhere else earlier in the day.
My two cents.
If using RH servers for mail, there was an issue, for some time like a
month, with Mimecast adding a silly "Content-type:
application/octet-stream" for mails which initially contained no such
header (additionnally, I noticed the issue only for mails which
contained a From: field in the body of the message).
This happened when both sending mails outside of RH, or when receiving
mails from outside in my experience.
The problem has been fixed (Mimecast rolled back the thing) around 04/25-04/26.
--
David Marchand
prev parent reply other threads:[~2022-05-03 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 16:17 Ben Woodard
2022-04-30 20:08 ` Mark Wielaard
2022-05-03 0:18 ` Ben Woodard
2022-05-03 10:52 ` David Marchand [this message]
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=CAJFAV8xkXfPVhoKj6XbGhi9PAMtmAY0nSBtOxDbGhpVXVuOMLQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=libabigail@sourceware.org \
--cc=mark@klomp.org \
--cc=vsoch@users.noreply.github.com \
--cc=woodard@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).