Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/5] avutil/tx_template: extend to 2M
Date: Mon, 24 Jul 2023 10:57:35 +0200
Message-ID: <CAPYw7P4H05TdoUczdJ6hpngt2NtVHj7Arj=Y7Agt1CgKGx0Qzw@mail.gmail.com> (raw)
In-Reply-To: <GV1P250MB0737326F7945D96D69EE40838F02A@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

On Mon, Jul 24, 2023 at 10:34 AM Andreas Rheinhardt <
andreas.rheinhardt@outlook.com> wrote:

> Michael Niedermayer:
> > On Sat, Jun 17, 2023 at 12:20:44AM +0200, Michael Niedermayer wrote:
> >> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> >> ---
> >>  libavutil/tx_template.c | 12 ++++++++++++
> >>  1 file changed, 12 insertions(+)
> >
> > will apply patches 1-4
> > (this should reduce the differences in the avradio repository in
> libavcodec/libavutil)
> >
>
> I actually wanted to complain about this; but then I saw that it had
> already been applied. Before that, I believed that this patchset was
> meant to be applied to the fork only and therefore didn't give it any
> scrutiny. These patches should have only been applied after the decision
> to merge the fork.
>
> I am against applying patches to simplify maintaining a fork. E.g. I am
> against further avpriv functions (but not absolutely) like you added in
> 4/5. Your patches are even very suboptimal in this regard: You added two
> avpriv functions, yet only one of them (the non-fixed-point) is used by
> your fork. Furthermore, you only need these 2MB windows for floats, not
> for int or doubles.
>
>
I need this, and only this patch to stay in tree.


> - Andreas
>
> _______________________________________________
> 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".
>
_______________________________________________
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-07-24  8:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 22:20 [FFmpeg-devel] [PATCH 0/5] add sdr support Michael Niedermayer
2023-06-16 22:20 ` [FFmpeg-devel] [PATCH 1/5] avutil/tx_template: extend to 2M Michael Niedermayer
2023-07-22 15:40   ` Michael Niedermayer
2023-07-23 17:48     ` Tomas Härdin
2023-07-24  8:59       ` Michael Niedermayer
2023-07-24 11:06         ` Leo Izen
2023-07-24 12:39           ` Thilo Borgmann
2023-07-24 13:04             ` Rémi Denis-Courmont
2023-07-24 15:45               ` Thilo Borgmann
2023-07-24  8:35     ` Andreas Rheinhardt
2023-07-24  8:57       ` Paul B Mahol [this message]
2023-07-24 18:46         ` Tomas Härdin
2023-07-25  6:14           ` Paul B Mahol
2023-06-16 22:20 ` [FFmpeg-devel] [PATCH 2/5] avcodec/pcm: allow Changing parameters Michael Niedermayer
2023-06-16 22:20 ` [FFmpeg-devel] [PATCH 3/5] avcodec/kbdwin: Support arbitrary sized windows Michael Niedermayer
2023-06-16 22:20 ` [FFmpeg-devel] [PATCH 4/5] avcodec: Rename ff_kbd_window_init() as it will be needed from outside libavcodec Michael Niedermayer
2023-06-16 22:20 ` [FFmpeg-devel] [PATCH 5/5] avformat: add sdr support Michael Niedermayer
2023-06-17  6:16   ` Paul B Mahol
2023-06-17  8:46     ` Michael Niedermayer
2023-06-17 11:08       ` Paul B Mahol
2023-06-17 12:48         ` Michael Niedermayer
2023-06-17 18:08           ` Paul B Mahol
2023-06-17 18:37             ` Michael Niedermayer
2023-06-17 18:43               ` Michael Niedermayer
2023-06-18 11:46               ` Paul B Mahol
2023-06-18 12:36                 ` Kieran Kunhya
2023-06-24 10:22                   ` Tomas Härdin
2023-06-18 12:59               ` Lynne
2023-06-18 13:30                 ` Hendrik Leppkes
2023-06-18 13:45                   ` Lynne
2023-06-18 13:48                 ` Michael Niedermayer
2023-06-17 13:30   ` Leo Izen
2023-06-17 18:10     ` 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='CAPYw7P4H05TdoUczdJ6hpngt2NtVHj7Arj=Y7Agt1CgKGx0Qzw@mail.gmail.com' \
    --to=onemda@gmail.com \
    --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