From: Niklas Haas via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>,
ffmpeg-devel@ffmpeg.org
Cc: Niklas Haas <ffmpeg@haasn.xyz>,
Timo Rothenpieler <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] CI
Date: Sat, 23 Aug 2025 00:37:00 +0200
Message-ID: <20250823003700.GB506012@haasn.xyz> (raw)
In-Reply-To: <26b1768d-e8b4-4c8f-84ce-4207d4399133@rothenpieler.org>
On Fri, 22 Aug 2025 17:22:54 +0200 Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> We could only run those tests on master, not on PRs.
> Nobody is impacted by them then, and we still notice breakage reasonably
> fast.
That seems reasonable to me.
_______________________________________________
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:[~2025-08-22 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 23:26 Michael Niedermayer via ffmpeg-devel
2025-08-20 15:56 ` Timo Rothenpieler via ffmpeg-devel
2025-08-20 19:25 ` Michael Niedermayer via ffmpeg-devel
2025-08-20 22:31 ` Timo Rothenpieler via ffmpeg-devel
2025-08-21 16:03 ` Kacper Michajlow via ffmpeg-devel
2025-08-21 21:16 ` Michael Niedermayer via ffmpeg-devel
2025-08-21 21:33 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 5:00 ` Kieran Kunhya via ffmpeg-devel
2025-08-22 12:13 ` Timo Rothenpieler via ffmpeg-devel
2025-08-22 14:51 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 14:54 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 15:22 ` Timo Rothenpieler via ffmpeg-devel
2025-08-22 18:48 ` Martin Storsjö via ffmpeg-devel
2025-08-22 20:31 ` Michael Niedermayer via ffmpeg-devel
2025-08-22 22:37 ` Niklas Haas 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=20250823003700.GB506012@haasn.xyz \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@haasn.xyz \
--cc=timo@rothenpieler.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