From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add entry for jpegxl*
Date: Mon, 16 Oct 2023 00:27:33 +0200 (CEST)
Message-ID: <NgpRuR7--7-9@lynne.ee> (raw)
In-Reply-To: <1f702757-7339-4c34-90f8-a87e064b9193@gmail.com>
Oct 15, 2023, 23:42 by leo.izen@gmail.com:
> On 10/15/23 09:11, Lynne wrote:
>
>> Oct 15, 2023, 14:14 by leo.izen@gmail.com:
>>
>>> Adding myself for jpegxl* in avcodec as I'm the maintainer of this
>>> parser.
>>>
>>> Signed-off-by: Leo Izen <leo.izen@gmail.com>
>>> ---
>>> MAINTAINERS | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index b5c116c3d4..b66c3d09a6 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -181,6 +181,7 @@ Codecs:
>>> interplayvideo.c Mike Melanson
>>> jni*, ffjni* Matthieu Bouron
>>> jpeg2000* Nicolas Bertrand
>>> + jpegxl* Leo Izen
>>> jvdec.c Peter Ross
>>> lcl*.c Roberto Togni, Reimar Doeffinger
>>> libcelt_dec.c Nicolas George
>>> @@ -434,8 +435,7 @@ Muxers/Demuxers:
>>> ipmovie.c Mike Melanson
>>> ircam* Paul B Mahol
>>> iss.c Stefan Gehrer
>>> - jpegxl_anim_dec.c Leo Izen
>>> - jpegxl_probe.* Leo Izen
>>> + jpegxl* Leo Izen
>>> jvdec.c Peter Ross
>>> kvag.c Zane van Iperen
>>> libmodplug.c Clément Bœsch
>>>
>>
>> Would you mind using jpegxl_parse*?
>>
>
> There's also jpegxl.h. If you add a decoder you can always change the MAINTAINERS entry then, at that time.
>
Sure, that's fair.
_______________________________________________
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".
prev parent reply other threads:[~2023-10-15 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 12:14 Leo Izen
2023-10-15 13:11 ` Lynne
2023-10-15 21:41 ` Leo Izen
2023-10-15 22:27 ` Lynne [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=NgpRuR7--7-9@lynne.ee \
--to=dev@lynne.ee \
--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