From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fate rsync switch to git
Date: Wed, 21 Feb 2024 02:39:42 +0100
Message-ID: <0fe648d5-d5b1-4cf3-a88f-0a5cf121e653@betaapp.fastmail.com> (raw)
In-Reply-To: <20240220143134.GT6420@pb2>
Yo,
On Tue, 20 Feb 2024, at 15:31, Michael Niedermayer wrote:
> 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 ?
Yes, that's my idea.
The git part is not for others clients to sync, but just to manage the samples.
It allows to have versioning of the samples, with the extra ability to have branches and tags matching the ffmpeg branches.
It avoids the weird dance "waiting for FATE admin to upload thing", because their would be multiple approvers/committers to that repo.
It simplifies the workflow on the admin side, since with a git hook, the server does "git update" in the directory that will be rsync'd by the mirrors. And it does not change their workflow, still using rsync.
just my 5c.
--
Jean-Baptiste Kempf - President
+33 672 704 734
_______________________________________________
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:[~2024-02-21 1:40 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
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 [this message]
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=0fe648d5-d5b1-4cf3-a88f-0a5cf121e653@betaapp.fastmail.com \
--to=jb@videolan.org \
--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