On Mon, Dec 5, 2016 at 10:48 AM Vittorio Giovara <vittorio.giov...@gmail.com> wrote:
> While it's great to hear that it was "found by Coverity in FFmpeg", it > would more useful to mention the CID number. > As you may know, Coverity is able to hash same issues in different > repositories, so by using the CID number it's possible to pinpoint the > problem in both Libav and FFmpeg. > > Would you resending them writing down the CID, or just reply back with > the CID and someone will edit the commit message? Are CIDs universal for both projects? I figured an FFmpeg CID is not useful for Libav. But either way for FFmpeg this patch is CID1396851. Timothy _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
