3 ms·
ergh. unfortunate. well, the project is already forked into libav, right? is development of that one going forward?
by allenbrunson 16y ago
ergh. unfortunate.
well, the project is already forked into libav, right? is development of that one going forward?
- DarkShikari 16y agoNothing has changed in terms of actual development trees: it was already previously forked into the videolan.org git tree (Michael's) and the ffmpeg.org git tree. The latter is now libav. Previously, Michael was doing massive amounts of cherry-picking from the other tree, since the vast majority of commits have been there. The big annoyance for users will be probably when the main tree (now libav) decides to bump the API to the next version. Michael will either be forced to import all the changes exactly, or end up with an incompatible API, which will cause NIGHTMARES, especially if they both have the same soname version!