From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mpegvideo: Remove spec-incompliant inverse quantisation
Date: Thu, 09 Nov 2023 22:52:19 +0200
Message-ID: <15041633.235GFhGzie@basile.remlab.net> (raw)
In-Reply-To: <ZU1E7wAtbdp-t3tk@metallschleimette>
Le torstaina 9. marraskuuta 2023, 22.45.35 EET Alexander Strasser a écrit :
> I can't see how the reason for the presence of code can be ultimately
> defined objectively and non-arbitrary.
Ultimately, this was discussed and decided in a meeting, which Michael
attended (albeit remotely) and for which meeting notes were published.
That being the case, I don't see why Andreas should have to perform extensive
testing and write extensive justification. He could have done and that would
have been nice, but that is all.
In this situation, it is up to whoever disagrees (and presumably was not in
the meeting) to provide extensive justification why the decision should be
reversed. And I'm not seeing any such thing.
Also anything to shrink the amount of MMX code Looks Good To Me.
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
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".
next prev parent reply other threads:[~2023-11-09 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 13:11 Andreas Rheinhardt
2023-10-30 18:40 ` Kieran Kunhya
2023-10-31 8:40 ` Michael Niedermayer
2023-11-08 11:40 ` Anton Khirnov
2023-11-08 20:55 ` Alexander Strasser
2023-11-08 22:58 ` Vittorio Giovara
2023-11-09 20:55 ` Alexander Strasser
2023-11-09 10:13 ` Anton Khirnov
2023-11-09 20:45 ` Alexander Strasser
2023-11-09 20:52 ` Rémi Denis-Courmont [this message]
2023-11-09 22:16 ` Michael Niedermayer
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=15041633.235GFhGzie@basile.remlab.net \
--to=remi@remlab.net \
--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