Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Forgejo entry threshold
Date: Mon, 11 Aug 2025 21:49:32 +0200
Message-ID: <20250811194932.GG1079928@pb2> (raw)
In-Reply-To: <29D4DB17-876E-4077-922D-3F4B4771A2E0@remlab.net>


[-- Attachment #1.1: Type: text/plain, Size: 1481 bytes --]

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@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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2025-08-11 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250804143901.82ED768C3C2@ffbox0-bg.ffmpeg.org>
2025-08-04 14:45 ` Nicolas George
2025-08-04 14:47   ` Hendrik Leppkes
2025-08-04 14:49     ` Nicolas George
2025-08-04 15:06   ` Leon Grutters
2025-08-05 13:10     ` Nicolas George
2025-08-05 14:17       ` Kacper Michajlow
2025-08-07 10:42         ` Nicolas George
2025-08-06  5:52     ` Rémi Denis-Courmont
2025-08-06  8:11       ` Nicolas George
2025-08-07 12:30         ` Rémi Denis-Courmont
2025-08-07 12:37           ` Nicolas George
2025-08-08  3:14             ` Rémi Denis-Courmont
2025-08-09 18:39               ` Nicolas George
2025-08-11 19:49               ` Michael Niedermayer [this message]
2025-08-05 13:07   ` Nicolas George

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=20250811194932.GG1079928@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git