Re: [FFmpeg-devel] Regarding Git Tooling

[Michael Niedermayer <michael@niedermayer.cc>]

[-- Attachment #1.1: Type: text/plain, Size: 2660 bytes --]

Hi

On Tue, Jan 21, 2025 at 01:56:09AM +0000, Soft Works wrote:
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Michael Niedermayer
> > Sent: Tuesday, January 21, 2025 2:26 AM
> > To: FFmpeg development discussions and patches <ffmpeg-
> > devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] Regarding Git Tooling
> 
> 
> > 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.
> 
> How is that supposed to work when the contributor is submitting to Forgejo (or whatever) and the maintainer uses the ML?

ATM we have contributors who would hapily submit to either and some that only
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? 

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 would
help her. Simple patches would get applied complex ones rejected with information
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://github.com/ffstaging/FFmpeg/wiki).

cool


> But this is still limited as it doesn't send PR comments back to the ML and it doesn't support mirroring patchsets from the ML back to GitHub and comments from GitHub back to the ML.

cant chatgpt be made to synchronize comments between mailing list and the web?


thx

[...]
-- 
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 ..."

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".