Hi Vittorio, The commits in this PR <https://bitbucket.org/multicoreware/x265_git/pull-requests/25> were picked and pushed to the master branch of x265.(b647da9 <https://bitbucket.org/multicoreware/x265_git/commits/b647da90fb6aeac20cd1228cd02af932b913db23> ,b153007 <https://bitbucket.org/multicoreware/x265_git/commits/b153007d1e10091a0ef38d16f1d8f35bc0437343> ,114af15 <https://bitbucket.org/multicoreware/x265_git/commits/114af1598c43c603a6d9473e5f1102efbebf9e27> ).
*Thanks,* *Kirithika* On Thu, Nov 28, 2024 at 10:36 PM Vittorio Giovara < vittorio.giov...@gmail.com> wrote: > On Thu, Nov 28, 2024 at 3:22 AM Kirithika Kalirathnam < > kirith...@multicorewareinc.com> wrote: > > > Hi All, > > > > x265 v4.1 <https://bitbucket.org/multicoreware/x265_git/branch/master> > is > > released with the fixes addressing memory leak and other reported > > issues.Please check it out. > > > > *Thanks,* > > *Kirithika* > > > > Hi Kirithika, > would you be able to also merge this one > https://bitbucket.org/multicoreware/x265_git/pull-requests/25 ? > It's triggering security alarms in the company internal checks - I've > already updated the PR once as requested, but there are new conflicts now. > Any chance you could help? > Thank you > -- > Vittorio > _______________________________________________ > 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". > _______________________________________________ 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".
