From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 1BAF14CEB6 for ; Thu, 13 Feb 2025 09:49:27 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 707F068BC65; Thu, 13 Feb 2025 11:49:22 +0200 (EET) Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 780CA68B4C3 for ; Thu, 13 Feb 2025 11:49:15 +0200 (EET) Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 4Ytr490tFlz9t0N for ; Thu, 13 Feb 2025 10:49:13 +0100 (CET) Message-ID: Date: Thu, 13 Feb 2025 15:19:10 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20250212180659.GP4991@pb2> <73f4b334-a4eb-4f06-b01e-e30988d49d1a@lynne.ee> <90f6d33f-65e1-4ff6-a30f-f1eee8f89d23@gmail.com> <8887ba88-7657-4432-a8c4-6d9d0eb33f8c@rothenpieler.org> <6a5a1ba9-08c3-40fe-9313-55f82889afa2@rothenpieler.org> Content-Language: en-US From: Gyan Doshi In-Reply-To: Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 2025-02-13 02:19 pm, Leo Izen 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. For some time, Github has allowed in-place editing. What that means is once you finished editing the file in the upstream repo, GH will fork the repo for you, or if already forked, create a new branch, with your changes incorporated, and give you an option to send a PR. Regards, Gyan _______________________________________________ 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".