Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Tanay Manerikar <manerikartanay05@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Thu, 13 Feb 2025 14:57:08 +0530
Message-ID: <CAF9S7Kdpz1Uh4+GCfbY2aOVyaC4X=9BqZ+kWYMjQX9miiDZBiA@mail.gmail.com> (raw)
In-Reply-To: <a2dc4440-5725-4c8a-981b-f6130b7bc8c3@gmail.com>

On Thu, Feb 13, 2025 at 2:20 PM Leo Izen <leo.izen@gmail.com> wrote:

> On 2/12/25 5:05 PM, Timo Rothenpieler wrote:
> >>
> > I'm really not sure what you're asking.
> > PRs are not restricted. Creating repos is.
> > And there is no way to NOT restrict it, unless you want to pay several
> > hundred Euros a month in hosting fees extra, and constantly be on the
> > lookout for hosting illegal/harmful things.
>
> My understanding as a Github and Gitlab user is the usual way to make a
> PR is to first fork the repository, then commit changes to a branch on
> your fork, and then send a PR which compares the fork to the master
> branch of upstream.
>
> If you can't make a repository, I'm not sure how you would do a PR. It
> sounds like you're saying there's another way to do it, but I'm not
> familiar with it and I expect many other people are not either.
>
> - Leo Izen (Traneptora)
>
I just created an account with  Forgejo, but I can't fork the main FFmpeg
repo. Who do I have to ask for access to create a repo? I am not sure if
this is the correct place to ask this.
- Tanay Manerikar
_______________________________________________
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-02-13  9:27 UTC|newest]

Thread overview: 41+ 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
2025-02-13 12:07                     ` Tomas Härdin
2025-02-13  4:05                   ` martin schitter
2025-02-13  8:49                   ` Leo Izen
2025-02-13  9:27                     ` Tanay Manerikar [this message]
2025-02-13 12:40                       ` Leo Izen
2025-02-13  9:49                     ` Gyan Doshi
2025-02-13 10:30                       ` Soft Works
2025-02-13 12:37                       ` Leo Izen
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-13  7:24                           ` Soft Works
2025-02-13 11:04                   ` Tobias Rapp
2025-02-13 12:07                     ` Soft Works
2025-02-13 12:27                       ` Soft Works
2025-02-13 12:10             ` Tomas Härdin
2025-02-13 12:38               ` martin schitter
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='CAF9S7Kdpz1Uh4+GCfbY2aOVyaC4X=9BqZ+kWYMjQX9miiDZBiA@mail.gmail.com' \
    --to=manerikartanay05@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