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 1EEAA49B16 for ; Tue, 21 Jan 2025 02:38:15 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 19B0168B6A7; Tue, 21 Jan 2025 04:38:12 +0200 (EET) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1AC7168A753 for ; Tue, 21 Jan 2025 04:38:06 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 4B13BE0002 for ; Tue, 21 Jan 2025 02:38:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1737427085; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Aw9+8ZGKITbovviVaQjlOVx0FGsBhFGIihNYW5W53DQ=; b=iAtp6iJbxtNa9sPAjyqEHtJAx+oqDNIE+mhLH6JFS5TMoOhGtxh/sxCK5ZtS9rz6gDMr+M ZtM5l7GIv81/LXSoHvUi4YAqVNwNhT+AX6gDN9cCyTW+ueyfn/2wszNBbwRgNobNskE/uV bnKLvoxbde7GsWOcprWLZDuE9O3FO8RGAsyqN95Tjcn5/lbyiL68uxKXbvjYNnC6sBBR0z uz5vw63R4uHwd1+//4tVlBFiU0It8Qpg6MpeV00o486mxagR7MGntyn3lCQDqeJKGELWNh yy3BpG2pd3IlxO4rVUQqabaOsRWpY0vdsc2j4vKoj96FmUZX77sd1A01JsRChA== Date: Tue, 21 Jan 2025 03:38:04 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20250121023804.GE4991@pb2> References: <20250121012624.GC4991@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Regarding Git Tooling 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-Type: multipart/mixed; boundary="===============1782073584922117300==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============1782073584922117300== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GkFMM18uj3x0cOpk" Content-Disposition: inline --GkFMM18uj3x0cOpk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Tue, Jan 21, 2025 at 01:56:09AM +0000, Soft Works wrote: > > -----Original Message----- > > From: ffmpeg-devel On Behalf Of > > Michael Niedermayer > > Sent: Tuesday, January 21, 2025 2:26 AM > > To: FFmpeg development discussions and patches > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] Regarding Git Tooling >=20 >=20 > > I dont know why the options are exclusive. One can add a Forgejo on > > ffmpeg.org > > but leave the Mailing List/Patch Workflow in place for cases where > > the > > maintainer or patch author prefers a ML workflow. >=20 > How is that supposed to work when the contributor is submitting to Forgej= o (or whatever) and the maintainer uses the ML? ATM we have contributors who would hapily submit to either and some that on= ly would submit to one type. Same for maintainers. that makes 9 combined cases (ML, ANY, WEB) x (ML, ANY, WEB) Currently 4 of these 9 cases work with what i suggest, 7 of 9 would work If more can be done with smart tools thats great The goal is to simplify everyones workflow, use all modern tools available to make it easier for people > How do they communicate?=20 The contributor looks in MAINTAINERS and sees if there is a preferred place= to submit a patch(set) to. If she submits to the wrong place likely people wou= ld help her. Simple patches would get applied complex ones rejected with infor= mation where to submit them. > How does the maintainer get notified that there's a PR available to fetch? Iam not sure i understand the question but teh same way as she is notified = of new commits in git, by runnning git fetch and seeing new things > And how does the maintainer comment on code when it wasn't sent to the ML? > Finally, how do the review comments flow back to the modern system? > > The only solution I know about which can do this is GitGitGadget (used by= the developers of Git itself) which I have adapted and set up (https://git= hub.com/ffstaging/FFmpeg/wiki). cool > But this is still limited as it doesn't send PR comments back to the ML a= nd it doesn't support mirroring patchsets from the ML back to GitHub and co= mments from GitHub back to the ML. cant chatgpt be made to synchronize comments between mailing list and the w= eb? thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The real ebay dictionary, page 1 "Used only once" - "Some unspecified defect prevented a second use" "In good condition" - "Can be repaird by experienced expert" "As is" - "You wouldnt want it even if you were payed for it, if you knew .= =2E." --GkFMM18uj3x0cOpk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZ48IiQAKCRBhHseHBAsP q89sAJ9u1XB5YuumVgejv+/T4ascDxrKqwCdHZh++TZFSaFECqYVyI6HhZfeaE4= =/abN -----END PGP SIGNATURE----- --GkFMM18uj3x0cOpk-- --===============1782073584922117300== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============1782073584922117300==--