Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fate rsync switch to git
Date: Tue, 20 Feb 2024 20:43:30 +0200
Message-ID: <CAEu79SZsz3M6E-YSwoWj0Q-CcuxWMg0EtOWe0kk5Vt8UxgJC0w@mail.gmail.com> (raw)
In-Reply-To: <20240220143134.GT6420@pb2>

On Tue, Feb 20, 2024 at 4:31 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi all
>
> I did hear (at fosdem?)
> about the idea to switch from rsync to git for managing the fate samples
> i thought the idea sounds interresting but isnt rsync more efficient ?
>

Do note that the idea was that this would only be for management of
the main archive, so it would not affect clients/runners rsync'ing
from the main archive.

Of course clients which want to sync directly from git could do that,
but the idea would be to keep the sync requirements same for FATE
clients/runners: if you are only running tests, rsync is enough.

As after all, the primary reasons for having the samples in git would
be versioning, more concrete known states in a public archive (I would
probably not call this a "backup", but it would mean we would have the
history in multiple places at least), as well as - if we utilize
something like git{lab,hub} - easier workflow to adding new samples by
means of f.ex. merge/pull requests.

This idea originated from looking at how the dav1d project handled
their reference sample suite, which seems to have served them well
enough: https://code.videolan.org/videolan/dav1d-test-data

Regards,
Jan
_______________________________________________
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:[~2024-02-20 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 14:31 Michael Niedermayer
2024-02-20 18:43 ` Jan Ekström [this message]
2024-02-21 14:38   ` Niklas Haas
2024-02-21 14:50     ` epirat07
2024-02-27 18:57       ` Vittorio Giovara
2024-02-21  1:39 ` Jean-Baptiste Kempf
2024-02-21  3:13   ` Zhao Zhili
2024-02-21 12:50   ` Michael Niedermayer

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=CAEu79SZsz3M6E-YSwoWj0Q-CcuxWMg0EtOWe0kk5Vt8UxgJC0w@mail.gmail.com \
    --to=jeebjp@gmail.com \
    --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