Timo Rothenpieler (HE12025-07-24): > I don't see any need for this, no. If the patch does not reach our inbox, it will not be reviewed.
> That's what it does, just not as format-patch, but simply as a link. A link is not enough. When we open our mail, we need to be able to see the proposed change without an extra step. > And the mailing list is "a monolithic thing" as well, so there's no point > throwing shade like that. The mailing-list is just a mailing list, it does not try to combine a dozen different tools into one. > Patchwork tries to do that and it only semi-works, so I'd rather not. Then stop trying to force us to use mediocre tools. > > # View it on FFmpeg Forgejo ( > > https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20031 ) or reply to this email > > directly. > > is not adequate. > Yes it is, the mailing list just eats the Reply-To address, breaking it. No it is not: it requires an extra step. > It's been mentioned multiple times on the list and on IRC by now, and it > should be obvious that you can't just give yourself push/merge access on > your own anyway. I do not care about push access for now, I care about notifications. As libabvfilter maintainer, if somebody proposes a patch on libavfilter, I need to see it. You promised it would be possible to continue working through mail without extra work: did you lie? -- Nicolas George _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
