[FFmpeg-devel] Forgejo entry threshold

[Michael Niedermayer]

Hi Remi

On Fri, Aug 08, 2025 at 10:14:52AM +0700, Rémi Denis-Courmont wrote:
> 
> 
> Le 7 août 2025 19:37:32 GMT+07:00, Nicolas George <george at nsup.org> a écrit :
> >Rémi Denis-Courmont (HE12025-08-07):
> >> Sure. You can send a list of patch files... And make it even more difficult to review,
> >
> >What? An attached file is not more difficult to review than a mail sent
> >directly by git,
> 

> If your mail client treats attachments the same as inline text, your mail client is very badly broken as a mail client. And if not, then it is obviously much more cumbersome to review an attachment.

mime_lookup application/octet-stream text/plain

auto_view text/x-patch text/x-diff

color body brightwhite default "^Index: .*"
color body red   default "^-.*"
color body green default "^[+].*"
color body white default "^ #.*"

First re-analyzes "application/octet-stream" and "text/plain" attachments and
provides them with the correct mime type according to what the file is

the second causes attachments that are patches to be shown

and third will colorize patches/diffs even when they are inline

I almost dont even notice if a patch is inline or an attachment, both
are shown automatically as i look at the mail

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20250811/5b25f697/attachment.sig>