Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Timo Rothenpieler <timo@rothenpieler.org>,
	Zhao Zhili <quinkblack@foxmail.com>
Subject: [FFmpeg-devel] [FFmpeg-devel][QUESTION] Add new sample to fate-suite via forgejo
Date: Thu, 18 Sep 2025 17:25:50 +0800
Message-ID: <tencent_6FD093E6E127D96A9693211C5A8B96E61706@qq.com> (raw)

Current situation:
1. A patch depends on new sample in fate-suit will fail CI
2. New sample needs to upload to fate-suit server manually

Question: Is it possible to hook sample uploading request to forgejo?

A simple idea is:
1. Setup a git repo with git-lfs support for fate-suit.
2. Add new sample via sending PR to this fate-suit repo.
3. Add cross link and rerun CI manually in FFmpeg repo’s PR after fate-suit’s PR merged.

Maybe there are more simpler methods to do that.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

             reply	other threads:[~2025-09-18  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18  9:25 Zhao Zhili via ffmpeg-devel [this message]
2025-09-18 14:27 ` [FFmpeg-devel] " Timo Rothenpieler 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=tencent_6FD093E6E127D96A9693211C5A8B96E61706@qq.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=quinkblack@foxmail.com \
    --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