From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] fate: add target to remove sample files that are no longer on the server Date: Sun, 27 Apr 2025 20:07:53 +0200 Message-ID: <20250427180753.2468146-1-michael@niedermayer.cc> (raw) Also add a target that shows what would be deleted Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> --- doc/fate.texi | 3 +++ tests/Makefile | 4 ++++ 2 files changed, 7 insertions(+) diff --git a/doc/fate.texi b/doc/fate.texi index 7a2e0edfcc6..0a90a6401be 100644 --- a/doc/fate.texi +++ b/doc/fate.texi @@ -44,6 +44,9 @@ targets and variables. If you want to run FATE on your machine you need to have the samples in place. You can get the samples via the build target fate-rsync. +You can also use fate-rsync-clean to also remove sample files that +no longer are on the server and fate-rsync-clean-dry to see what would +be removed. Use this command from the top-level source directory: @example diff --git a/tests/Makefile b/tests/Makefile index 0c08f687130..d1e754247a0 100644 --- a/tests/Makefile +++ b/tests/Makefile @@ -283,6 +283,10 @@ ifdef SAMPLES FATE += $(FATE_EXTERN) fate-rsync: rsync $(RSYNC_OPTIONS) rsync://fate-suite.ffmpeg.org/fate-suite/ $(SAMPLES) +fate-rsync-clean-dry: + rsync $(RSYNC_OPTIONS) --delete --dry-run rsync://fate-suite.ffmpeg.org/fate-suite/ $(SAMPLES) +fate-rsync-clean: + rsync $(RSYNC_OPTIONS) --delete rsync://fate-suite.ffmpeg.org/fate-suite/ $(SAMPLES) else fate:: @echo "warning: only a subset of the fate tests will be run because SAMPLES is not specified" -- 2.49.0 _______________________________________________ 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".
reply other threads:[~2025-04-27 18:08 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250427180753.2468146-1-michael@niedermayer.cc \ --to=michael@niedermayer.cc \ --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