Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc: deprecate avcodec_dct, av_fft, av_dct, av_rdft and av_mdct
Date: Mon, 20 Feb 2023 16:34:17 +0100
Message-ID: <167690725750.10789.9937672407163101400@lain.khirnov.net> (raw)
In-Reply-To: <NO_00XT--3-9@lynne.ee>

Quoting Lynne (2023-02-18 15:53:32)
> Feb 18, 2023, 14:58 by jamrial@gmail.com:
> > vf_spp should be ported to tx, not the avdct functions silenced. You're just scheduling a compilation failure as is.
> There's enough time to port it, a whole year in fact.

Past experience shows that it never works like this. It's either ported
now or you're forcing somebody else to do it before the next bump.
I vastly prefer the former.

-- 
Anton Khirnov
_______________________________________________
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".

  reply	other threads:[~2023-02-20 15:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:54 Lynne
2023-02-17 17:08 ` James Almer
2023-02-17 18:45   ` Lynne
2023-02-17 23:59     ` Hendrik Leppkes
2023-02-18 11:52       ` Lynne
2023-02-18 13:15         ` James Almer
     [not found]   ` <NOVgRri--3-9@lynne.ee-NOVgVXs----9>
2023-02-18 12:49     ` Lynne
2023-02-18 13:32       ` James Almer
2023-02-18 13:45         ` Lynne
2023-02-18 13:58           ` James Almer
2023-02-18 14:53             ` Lynne
2023-02-20 15:34               ` Anton Khirnov [this message]
2023-02-20 17:18                 ` Lynne
2023-02-20 17:22                   ` Anton Khirnov
2023-02-20 17:35                     ` Lynne
     [not found]             ` <NO_00XT--3-9@lynne.ee-NO_04wO----9>
2023-02-19 18:47               ` Lynne

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=167690725750.10789.9937672407163101400@lain.khirnov.net \
    --to=anton@khirnov.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