From: Leo Izen <leo.izen@gmail.com>
To: FFmpeg Development <ffmpeg-devel@ffmpeg.org>
Cc: samples-request@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/jpegxl_parser: fix parsing sequences of extremely small files
Date: Sun, 26 Nov 2023 18:33:51 -0500
Message-ID: <c9a71af4-e3fb-4b1b-a55c-4a596b7d0835@gmail.com> (raw)
In-Reply-To: <680FD2DE-0927-41D5-941A-C56E17672521@mail.de>
On 11/26/23 13:07, Thilo Borgmann wrote:
>
>
>> Am 26.11.2023 um 14:47 schrieb Leo Izen <leo.izen@gmail.com>:
>> On 11/26/23 05:56, Anton Khirnov wrote:
>>> Would be nice to have tests for these.
>>
>> I have a sample at: https://buzo.us/l.jxl
>>
>> It would test both of these patches. I can send a fate test for these to the ML if the sample gets uploaded. I CC'd samples-request@ffmpeg.org as well.
>
> Can do this in a bit. What about the file you‘d sent to samples-request in August, is there still a test to be pushed about it as well?
>
> -Thilo
There is not, that sample from August was already uploaded and the fate
test utilizing it has been merged.
- Leo Izen (Traneptora)
_______________________________________________
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-26 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 23:45 [FFmpeg-devel] [PATCH 0/2] JPEG XL parser bug fixes Leo Izen
2023-11-23 23:45 ` [FFmpeg-devel] [PATCH 1/2] avcodec/jpegxl_parse{, r}: use correct ISOBMFF extended size location Leo Izen
2023-11-23 23:45 ` [FFmpeg-devel] [PATCH 2/2] avcodec/jpegxl_parser: fix parsing sequences of extremely small files Leo Izen
2023-11-26 10:56 ` Anton Khirnov
2023-11-26 13:47 ` Leo Izen
2023-11-26 18:07 ` Thilo Borgmann via ffmpeg-devel
2023-11-26 23:33 ` Leo Izen [this message]
2023-11-27 9:49 ` Thilo Borgmann via ffmpeg-devel
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=c9a71af4-e3fb-4b1b-a55c-4a596b7d0835@gmail.com \
--to=leo.izen@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=samples-request@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