From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] mimetype: add entry for .patch extension
Date: Wed, 10 Feb 2021 07:31:35 +0000 (UTC) [thread overview]
Message-ID: <339fdc13-8fbd-46bb-ac4e-69f44a8844b7@sirjofri.de> (raw)
In-Reply-To: <6B2624687B48229BD4C2C356D0661C68@eigenstate.org>
09.02.2021 06:08:56 ori@eigenstate.org:
> Quoth Michael Forney <mforney@mforney.org>:
>> This way, upas/vf won't flag .patch files as suspicious by default.
>>
>> diff [...]
>
> 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.
If you don't think about mail, but http servers: at least rc-httpd uses
it to construct content-type headers. It extends this list (which btw
doesn't include css and js). I'm not sure about ip/httpd or tcp80.
I have some extensions for rc-httpd I did for gridchat-web, that included
basic range handling as well as POST. I wanted to prepare a patch. It's
on https://github.com/sirjofri/gridchat-web, if someone else wants to do
it (it's very easy, but contains one auxiliary native program for range
handling. I can try some chain using cat file | {read -c $start
>/dev/null; read -c $end} instead and see if it's faster than dd. Sorry
for offtopic).
sirjofri
next prev parent reply other threads:[~2021-02-10 7:37 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)
2021-02-10 7:31 ` sirjofri [this message]
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=339fdc13-8fbd-46bb-ac4e-69f44a8844b7@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.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).