From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Thu, 13 Feb 2025 01:27:25 +0100
Message-ID: <e60a3ce8-88d3-4cae-acae-d5ab3c05715c@rothenpieler.org> (raw)
In-Reply-To: <CABGuwEksVLEyqS6hDQpjcdYD4-34nnJTFXat2XYAxCA3JAN_AQ@mail.gmail.com>
On 13.02.2025 00:34, Kieran Kunhya via ffmpeg-devel wrote:
> Yes but surely if users do a simple clone of the main repository, they will
> get all the branches of hundred of different pull requests?
No, why would they?
That's all abstracted away. Pretty much just an optimization on storage,
making all forks share the actual git object files.
Which has the side-effect that even on Github you can fork the FFmpeg
repo, push something, and then link to the hash of what you pushed on
the actual FFmpeg repo:
> https://github.com/FFmpeg/FFmpeg/commit/4904c8861b1b52c50199e83620fbabfad4733a2b
This commit is only on a branch of mine, not on any FFmpeg branch.
Github warns about that these days, but Gitlab/Gitea/Forgejo/... don't
for what I'm aware.
_______________________________________________
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:[~2025-02-13 0:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:06 Michael Niedermayer
2025-02-12 18:49 ` Lynne
2025-02-12 18:53 ` Romain Beauxis
2025-02-12 19:23 ` Lynne
2025-02-12 21:22 ` Stephen Hutchinson
2025-02-12 21:32 ` Timo Rothenpieler
2025-02-12 21:37 ` Soft Works
2025-02-12 21:51 ` Timo Rothenpieler
2025-02-12 22:01 ` Soft Works
2025-02-12 22:05 ` Timo Rothenpieler
2025-02-12 22:16 ` Soft Works
2025-02-12 23:29 ` Timo Rothenpieler
2025-02-12 23:34 ` Kieran Kunhya via ffmpeg-devel
2025-02-13 0:27 ` Timo Rothenpieler [this message]
2025-02-13 4:05 ` martin schitter
2025-02-12 22:12 ` Romain Beauxis
2025-02-12 23:22 ` Soft Works
2025-02-12 23:07 ` Soft Works
2025-02-12 23:34 ` Timo Rothenpieler
2025-02-13 0:17 ` Soft Works
2025-02-13 0:24 ` Romain Beauxis
2025-02-13 0:40 ` Soft Works
2025-02-13 1:52 ` Timo Rothenpieler
2025-02-13 2:59 ` Soft Works
2025-02-13 6:14 ` Lynne
2025-02-13 6:50 ` martin schitter
2025-02-13 6:54 ` Soft Works
2025-02-12 20:38 ` 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=e60a3ce8-88d3-4cae-acae-d5ab3c05715c@rothenpieler.org \
--to=timo@rothenpieler.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