From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org, ori@eigenstate.org
Subject: Re: [9front] mimetype: add entry for .patch extension
Date: Tue, 09 Feb 2021 18:54:10 -0800 [thread overview]
Message-ID: <1efc23b43baf1fb5@orthanc.ca> (raw)
In-Reply-To: <6B2624687B48229BD4C2C356D0661C68@eigenstate.org>
ori@eigenstate.org writes:
> Seems good, but for most purposes, it also seems
> reasonable to just 'rm /mail/lib/validateattachment';
> I don't think it really does anything useful for mail
> on plan 9.
+1. Cheking against file extensions tells you nothing. It has
always puzzled me why software that cares about this doesn't look
at the actual content ala 'file -m'.
next prev parent reply other threads:[~2021-02-10 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 23:07 Michael Forney
2021-02-09 5:08 ` ori
2021-02-10 2:54 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2021-02-10 7:31 ` sirjofri
2021-02-10 12:18 ` hiro
2021-02-10 21:59 ` Michael Forney
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=1efc23b43baf1fb5@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.org \
--cc=ori@eigenstate.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).