Hi all Id like to announce that ive setup a repository to merge pauls work of the last 2 years.
* Currently ive merged everything up to first february 2025
* all fate tests pass
* Some filters and decoders where split in 2 versions
thats because either teh added chanegs are buggy, break API/cmd line
interface
or plain the 2 versions are actively developed and too diverged
Note the license of this code is a bit wonky. The files have one
license and theres another one in LICENSE.md.
While I belives legally this allows one to choose either. I suggest
you check this with a lawyer.
g...@git.ffmpeg.org:almpeg
all ffmpeg developers should have write access to it (if you dont,
send me private mail/ping and expect 1-2 days to fix)
If you want to fix any mistakes in this, thats welcome!
currently gitlog mails are just sent to me, this can be changed if people want
Now, what is this good for ?
Once teh merges match the current date, we can either
* just merge it (with 0 conflicts)
* cherry pick from it easily (its closer to FFmpeg)
We can also for the cherry picking easily collaborate
using the almpeg repository and commit requested changes from
patch review to it
PS: today it seems a merge between master and almpeg has just 22 conflicts
a direct merge from pauls code with master has 1145 conflicts
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Many things microsoft did are stupid, but not doing something just because
microsoft did it is even more stupid. If everything ms did were stupid they
would be bankrupt already.
signature.asc
Description: PGP signature
_______________________________________________ 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".
