From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Jamaika1 <code@ffmpeg.org>, Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] Added new celt with opus 1.5.2 (PR #20716)
Date: Sun, 19 Oct 2025 15:26:05 +0200
Message-ID: <aPTm7bvGml2soaeo@phare.normalesup.org> (raw)
In-Reply-To: <176080841895.62.830144648391342506@bf907ddaa564>
Jamaika1 via ffmpeg-devel (HE12025-10-18):
> PR #20716 opened by Jamaika1
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20716
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20716.patch
>
>
> >From f1276fe5217d07fda6d7dba77d0740a32d4fdc15 Mon Sep 17 00:00:00 2001
> From: Jamaika1 <lukaszcz18@wp.pl>
> Date: Sat, 18 Oct 2025 17:26:10 +0000
> Subject: [PATCH] Added new celt with opus 1.5.2
>
> ---
> libavcodec/libcelt_dec.c | 31 ++++++++++++++++---------------
> 1 file changed, 16 insertions(+), 15 deletions(-)
Thanks for the patch. Can you explain why it is useful or necessary?
Preferably in the commit message.
By the way, the first line of the commit message must start with
something like: “lavc/libcelt_dec:”.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-10-19 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 17:26 [FFmpeg-devel] " Jamaika1 via ffmpeg-devel
2025-10-19 13:26 ` Nicolas George via ffmpeg-devel [this message]
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=aPTm7bvGml2soaeo@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@ffmpeg.org \
--cc=george@nsup.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