Hi Sean,
no problem, any task like that is kind of fun for me. Once I have finished
reviewing the bug list I plan to start with the format code cleanup.
Regards.
PaoloB
On Mon, Aug 10, 2015 at 3:48 PM, Sean McGovern gsean...@gmail.com wrote:
Hi Paolo,
Thank you very much for taking on
On 08/08/15 16:01, Paolo Bizzarri wrote:
Hi,
I am reviewing the bug list to see if some of the bugs listed as new are in
fact already fixed.
I was looking at Bug 825 - Invalid memory writes with libavresample.
https://bugzilla.libav.org/show_bug.cgi?id=825
It seems that it can be
Hi Paolo,
Thank you very much for taking on this task. It has been in my queue for some
time and I admit I haven't allocated appropriate cycle for it.
It is much appreciated. :)
-- Sean McG.
___
libav-devel mailing list
libav-devel@libav.org
On Sun, Aug 9, 2015 at 1:55 PM, Paolo Bizzarri pibi...@gmail.com wrote:
Hi,
I have started reviewing bugs in tracker from 1-100. They are 21.
Of them, the following two bugs have been fixed can be closed.
61 Matroska demuxer unable to play valid file without Cues section
95 Memory Blow-up
Hi,
I have started reviewing bugs in tracker from 1-100. They are 21.
Of them, the following two bugs have been fixed can be closed.
61 Matroska demuxer unable to play valid file without Cues section
95 Memory Blow-up in avconv when attempting to convert IDCIN source
They have both a sample
Hi,
I was looking at the open bugs, trying to figure out which ones should be
closed. So I went through the repository and checked commit for bug fixes
that correspond to bug still open.
This is the bug I have found. For each bug I have reported the link to the
bug, the author of the fix and the
On 09/08/15 10:32, Paolo Bizzarri wrote:
Hi,
I was looking at the open bugs, trying to figure out which ones should be
closed. So I went through the repository and checked commit for bug fixes
that correspond to bug still open.
This is the bug I have found. For each bug I have reported
Hi,
I am reviewing the bug list to see if some of the bugs listed as new are in
fact already fixed.
I was looking at Bug 825 - Invalid memory writes with libavresample.
https://bugzilla.libav.org/show_bug.cgi?id=825
It seems that it can be closed.
Luca posted a patch here:
