From: Laszlo Ersek <lersek@redhat.com>
To: Rebecca Cran <rebecca@bluestop.org>,
stephano <stephano.cetola@linux.intel.com>,
edk2-devel@lists.01.org, Leif Lindholm <leif.lindholm@linaro.org>,
Andrew Fish <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Doran, Mark" <mark.doran@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>
Subject: Re: Event Invitation: TianoCore Community Meeting - NAMO / EMEA
Date: Mon, 8 Oct 2018 13:01:54 +0200 [thread overview]
Message-ID: <d068dc3c-86f5-5ad0-1de4-1d4ddbfcc9e4@redhat.com> (raw)
In-Reply-To: <36beb58f-94f2-cd9f-b954-bfc0d15594c5@bluestop.org>
On 10/05/18 22:43, Rebecca Cran wrote:
> I don't see any information about time/place/etc. - should there be an
> attachment?
There is an attachment on the original invite email, called "invite.cs".
I see it on the instance of the invite that I got in my inbox directly,
not reflected from the list (because I was named personally on the
invite). However, the attachment is missing from the email reflected by
the list software.
This is not surprising: the edk2-devel list configuration strips all (or
most) attachments. If I remember correctly, I've complained about this
earlier -- such a list config is broken. It prevents people from sending
screenshots (well-compressed PNG screenshots of virtual machines are a
few tens of KB, they are perfectly suitable for mailing lists). It also
prevents people from sending compressed log files in attachments. IIRC
at one point I also had to base64-encode some binary file manually, and
embed it in the normal body of the email, because I wanted the mailing
list *archive* to preserve it.
At least with the TianoCore Bugzilla, we have another option for saving
binary artifacts necessary for debugging / bug reporting. The mailing
list config remains broken however.
Thanks
Laszlo
prev parent reply other threads:[~2018-10-08 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 19:39 Event Invitation: TianoCore Community Meeting - NAMO / EMEA stephano
2018-10-05 20:43 ` Rebecca Cran
2018-10-05 22:29 ` stephano
2018-10-08 11:01 ` Laszlo Ersek [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-list 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=d068dc3c-86f5-5ad0-1de4-1d4ddbfcc9e4@redhat.com \
--to=devel@edk2.groups.io \
/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