Le 23 novembre 2024 01:19:12 GMT+02:00, Michael Niedermayer <mich...@niedermayer.cc> a écrit : >Hi Remi > >On Fri, Nov 22, 2024 at 11:04:50PM +0200, Rémi Denis-Courmont wrote: >> Le perjantaina 22. marraskuuta 2024, 20.45.39 EET Michael Niedermayer a >> écrit >[...] >> > not just treat it as if split out means deleting it from ffmpeg. >> >> Err, but yes. From the perspective of FFmpeg-devel, once libpostproc is spun >> off from FFmpeg, then it is no longer maintained by FFmpeg developers. So we >> _must_ treat the hypothesis as a deletion from FFmpeg. > >If libpostproc is split off i would work on libpostproc. >And i will ensure that the development environment there will be free of these >kind of debates. Meaning i and others can do several times more usefull work. >Also libpostproc is GPL and compatible with a wide range of GPL filters >that could then be provided through a new libpostproc interface > > >[...] >> > also git history must be bisectable, and future changes from ffmpeg >> > buildsystem must be merged >> >> WTH? It would take an insane amount of time to rewrite a synthetic bisectable >> history. That would definitely not be worth the effort (or not worth paying >> someone hourly wage for it anyway). > >so now its an insane amount of time ?
No. Preserving history is a five-minute job with git-subtree or similar, and worth a few €. Rewriting it to be susceptible to bisection is months of useless busy work that is NOT worth the time spent. An expert with your skills has much more useful and valuable contributions to make than rewrite git history. >before its not worth 5k > >and yes, my split out code is fully bisectable and mergeble, in fact >that part of the work was not hard. Rewriting history makes zero economical sense, especially for a project that sees so little usage. >The FFmepg community did in the past want libpostproc split out. Nobody objected to that. We are objecting to your quote for it, in light of an existing implementation and competitive quote from Derek of 0€. > Thats >what the people at the time who spoke up wanted. Now some people >think its a bad idea, and some people argue about the cost or what exactly >should be done. You don't need to tell me that. You're the one taking the task hostage by insisting that it be done by you on your terms. _______________________________________________ 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".
