op== is confusing, as it may easily be mistook for an equality check,
while in reality it is doing an assigment to '='.
This patch has the additional benefit of cleaning up 2 warnings from
shellcheck.net.
Signed-off-by: Ganesh Ajjanagadde
---
configure | 4 ++--
1 file changed, 2 insertions(+),
Hi,
Apologies for not using git send-email for the remaining patches; it
seems like git send-email has been broken by gmail; or does not like
sending multiple patches in a single shot.
As these patches are trivial; I have attached the remainder instead to
this email.
Regards,
Ganesh
From d0471ed
Signed-off-by: Ganesh Ajjanagadde
---
libavfilter/vsrc_mandelbrot.c | 166 +-
1 file changed, 83 insertions(+), 83 deletions(-)
diff --git a/libavfilter/vsrc_mandelbrot.c b/libavfilter/vsrc_mandelbrot.c
index e26fecd..56d0503 100644
--- a/libavfilter/vsrc_
On Sat, Sep 12, 2015 at 08:34:14PM -0400, Alex Agranovsky wrote:
> My bad — sorry about that.
>
> On September 12, 2015 at 7:08:34 PM, Michael Niedermayer (michae...@gmx.at)
> wrote:
>
> On Sat, Sep 12, 2015 at 06:49:41PM -0400, Alex Agranovsky wrote:
> > Modified patch is attached.
> >
>
My bad — sorry about that.
On September 12, 2015 at 7:08:34 PM, Michael Niedermayer (michae...@gmx.at)
wrote:
On Sat, Sep 12, 2015 at 06:49:41PM -0400, Alex Agranovsky wrote:
> Modified patch is attached.
>
> --
> Alex Agranovsky
> Sighthound, Inc
> www.sighthound.com
>
This is as intended: stopping at the empty line is exactly what we should do in
this case, as it separates headers from the content.
If the two headers we’re looking for hadn’t been encountered prior to the empty
line, error should be returned.
This is based on http://tools.ietf.org/html/rfc204
On Sat, Sep 12, 2015 at 07:04:26PM -0400, Alex Agranovsky wrote:
> You’re correct, sir. New patch is attached.
>
>
> --
> Alex Agranovsky
> Sighthound, Inc
> www.sighthound.com
>
> On September 12, 2015 at 5:54:23 PM, Michael Niedermayer (michae...@gmx.at)
> wrote:
>
> On Sat, Sep
On Sat, Sep 12, 2015 at 06:49:41PM -0400, Alex Agranovsky wrote:
> Modified patch is attached.
>
> --
> Alex Agranovsky
> Sighthound, Inc
> www.sighthound.com
>
> On September 12, 2015 at 5:37:51 PM, Michael Niedermayer (michae...@gmx.at)
> wrote:
>
> On Sat, Sep 12, 2015 at 04:33:
Attached.
--
Alex Agranovsky
Sighthound, Inc
www.sighthound.com
On September 12, 2015 at 5:41:56 PM, Michael Niedermayer (michae...@gmx.at)
wrote:
On Sat, Sep 12, 2015 at 05:10:06PM -0400, Alex Agranovsky wrote:
> libavformat/mpjpegdec.c | 15 +++
> 1 file change
You’re correct, sir. New patch is attached.
--
Alex Agranovsky
Sighthound, Inc
www.sighthound.com
On September 12, 2015 at 5:54:23 PM, Michael Niedermayer (michae...@gmx.at)
wrote:
On Sat, Sep 12, 2015 at 05:05:04PM -0400, Alex Agranovsky wrote:
> Amended: one of the new block
Modified patch is attached.
--
Alex Agranovsky
Sighthound, Inc
www.sighthound.com
On September 12, 2015 at 5:37:51 PM, Michael Niedermayer (michae...@gmx.at)
wrote:
On Sat, Sep 12, 2015 at 04:33:17PM -0400, Alex Agranovsky wrote:
> libavformat/mpjpegdec.c | 2 +-
> 1 file ch
On Sat, Sep 12, 2015 at 07:52:42PM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached is a new patch that should be ready to be applied no matter if we
> drop compatibility or not.
>
> Please comment (quickly if possible), Carl Eugen
i think there are a few changes missing:
libavcodec/cook.c: I
On Sat, Sep 12, 2015 at 05:05:04PM -0400, Alex Agranovsky wrote:
> Amended: one of the new blocks ended up in a wrong location.
>
> libavformat/mpjpegdec.c | 19 +++
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegde
On Sat, Sep 12, 2015 at 05:10:06PM -0400, Alex Agranovsky wrote:
> libavformat/mpjpegdec.c | 15 +++
> 1 file changed, 15 insertions(+)
patching file libavformat/mpjpegdec.c
patch: malformed patch at line 6: return 0;
it seems the patches have been corrupted somewhere in th
On Sat, Sep 12, 2015 at 04:33:17PM -0400, Alex Agranovsky wrote:
> libavformat/mpjpegdec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegdec.c
> index b8281fc..8413ae7 100644
> --- a/libavformat/mpjpegdec.c
> +++ b/libavformat
libavformat/mpjpegdec.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegdec.c
index 1661b9d..009bbaf 100644
--- a/libavformat/mpjpegdec.c
+++ b/libavformat/mpjpegdec.c
@@ -40,6 +40,19 @@ static int get_line(AVIOContext *pb, char *lin
Amended: one of the new blocks ended up in a wrong location.
libavformat/mpjpegdec.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegdec.c
index 8413ae7..1661b9d 100644
--- a/libavformat/mpjpegdec.c
+++ b/libavfo
Signed-off-by: Paul B Mahol
---
libavfilter/Makefile | 1 +
libavfilter/af_stereowiden.c | 167 +++
libavfilter/allfilters.c | 1 +
3 files changed, 169 insertions(+)
create mode 100644 libavfilter/af_stereowiden.c
diff --git a/libavfilter
libavformat/mpjpegdec.c | 22 ++
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegdec.c
index 8413ae7..c1ca508 100644
--- a/libavformat/mpjpegdec.c
+++ b/libavformat/mpjpegdec.c
@@ -43,11 +43,22 @@ static int get_line(AV
Just a reminder if an *active developer* wants access to Coverity Scan
reports just ask. You can get low volume, occasional emails detailing
found defects, and/or access the info via the Coverity Scan site.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpe
libavformat/mpjpegdec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/mpjpegdec.c b/libavformat/mpjpegdec.c
index b8281fc..8413ae7 100644
--- a/libavformat/mpjpegdec.c
+++ b/libavformat/mpjpegdec.c
@@ -165,7 +165,7 @@ static int parse_multipart_header(AVFormatCont
On Sat, Sep 12, 2015 at 06:36:33PM +, Paul B Mahol wrote:
> On 9/11/15, Paul B Mahol wrote:
> > On 9/11/15, Rodger Combs wrote:
> >> ---
> >> libavcodec/adpcm.c | 6 +++---
> >> 1 file changed, 3 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
> >
James Almer gmail.com> writes:
> "NO direct access" will now apply to the new
> max_analyze_duration and probesize fields when
> incompatible-libav-abi is not used. Is that
> intended?
This is how the patch was ok'ed before.
I am 100% fine with moving the 64 bit fields,
but it is imo unrelat
On 9/12/2015 3:42 PM, Michael Niedermayer wrote:
> I think theres consense about "abi compatibility" so i would tend to
> suggest to move forward with that in mind.
In that case we should go ahead and don't bother with the
AV_HAVE_INCOMPATIBLE_LIBAV_ABI check at all for this change.
__
Sure thing — will split and resubmit.
--
Alex Agranovsky
Sighthound, Inc
www.sighthound.com
On September 12, 2015 at 2:37:52 PM, Michael Niedermayer (michae...@gmx.at)
wrote:
On Sat, Sep 12, 2015 at 02:06:28PM -0400, Alex Agranovsky wrote:
> Michael, thanks!
>
> Is the othe
On Sat, Sep 12, 2015 at 03:37:08PM -0300, James Almer wrote:
> On 9/12/2015 3:28 PM, Michael Niedermayer wrote:
> > On Sat, Sep 12, 2015 at 03:25:05PM -0300, James Almer wrote:
> >> On 9/12/2015 3:04 PM, Carl Eugen Hoyos wrote:
> >>> Hi!
> >>>
> >>> Attached patch implements making probesize and an
On Sat, Sep 12, 2015 at 02:06:28PM -0400, Alex Agranovsky wrote:
> Michael, thanks!
>
> Is the other change (mpjpegdec.c) still in review, or had it been overlooked
> due to not being included in the amended patch?
i didnt overlook them but they include several changes that could be
argued to be
On 9/12/2015 3:28 PM, Michael Niedermayer wrote:
> On Sat, Sep 12, 2015 at 03:25:05PM -0300, James Almer wrote:
>> On 9/12/2015 3:04 PM, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> Attached patch implements making probesize and analyzeduration 64bit
>>> unless api compatibility was requested.
>>>
>>>
On 9/11/15, Paul B Mahol wrote:
> On 9/11/15, Rodger Combs wrote:
>> ---
>> libavcodec/adpcm.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
>> index 52d0d44..ba38041 100644
>> --- a/libavcodec/adpcm.c
>> +++ b/libavcode
On Sat, Sep 12, 2015 at 03:25:05PM -0300, James Almer wrote:
> On 9/12/2015 3:04 PM, Carl Eugen Hoyos wrote:
> > Hi!
> >
> > Attached patch implements making probesize and analyzeduration 64bit
> > unless api compatibility was requested.
> >
> > I will add a line to doc/APIchanges and do a minor
On Sat, Sep 12, 2015 at 10:57:37PM +1000, Matt Oliver wrote:
> On 12 September 2015 at 19:40, Peter Belkner wrote:
>
> > On 12.09.2015 11:15, Geek.Song wrote:
> >
> >> diff -u
> >
> >
> LGTM.
> I had an identical patch ready to fix the same problem so this one is fine.
i think you dont have git
On 9/12/2015 3:04 PM, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch implements making probesize and analyzeduration 64bit
> unless api compatibility was requested.
>
> I will add a line to doc/APIchanges and do a minor version bump.
>
> Please review, this cannot wait, Carl Eugen
You're rem
On Sat, Sep 12, 2015 at 08:04:34PM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> Attached patch implements making probesize and analyzeduration 64bit
> unless api compatibility was requested.
>
> I will add a line to doc/APIchanges and do a minor version bump.
>
> Please review, this cannot wait, Ca
Michael, thanks!
Is the other change (mpjpegdec.c) still in review, or had it been overlooked
due to not being included in the amended patch?
-Best.
- Alex
--
Alex Agranovsky
Sighthound, Inc
www.sighthound.com
On September 11, 2015 at 6:43:31 PM, Michael Niedermayer (michae...@g
Hi!
Attached patch implements making probesize and analyzeduration 64bit
unless api compatibility was requested.
I will add a line to doc/APIchanges and do a minor version bump.
Please review, this cannot wait, Carl Eugen
diff --git a/libavformat/avformat.h b/libavformat/avformat.h
index b7f18c
On date Saturday 2015-09-12 16:13:53 +0200, Stefano Sabatini encoded:
> On date Monday 2015-09-07 11:37:47 +0200, Stefano Sabatini encoded:
> > Hi,
> >
> > I propose to have an official IRC meeting on the next Saturday, and I
> > propose the tentative time of 15:00 UTC, but feel free to propose a
Hi!
Attached is a new patch that should be ready to be applied no matter if we
drop compatibility or not.
Please comment (quickly if possible), Carl Eugen
diff --git a/doc/APIchanges b/doc/APIchanges
index 958035c..415463a 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -15,6 +15,10 @@ libav
Michael Niedermayer gmx.at> writes:
> > img2dec.c | 26 --
> > 1 file changed, 20 insertions(+), 6 deletions(-)
> > 322ea95b4166f9aa6a8a2d10366b665c933ab162 patchimg2mjpeg.diff
> > diff --git a/libavformat/img2dec.c b/libavformat/img2dec.c
>
> LGTM
Patch applied.
Th
On Sat, Sep 12, 2015 at 10:50 AM, Stefano Sabatini wrote:
> On date Saturday 2015-09-12 16:27:56 +0200, Nicolas George encoded:
>> Le sextidi 26 fructidor, an CCXXIII, Michael Niedermayer a écrit :
>> > + gitorious.org. And posting a merge request to the ffmpeg-devel
>> > mailing list.
>>
>>
On date Saturday 2015-09-12 16:27:56 +0200, Nicolas George encoded:
> Le sextidi 26 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> > + gitorious.org. And posting a merge request to the ffmpeg-devel
> > mailing list.
>
> Please no. The patches themselves need to go to the mailing list
Le sextidi 26 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> + gitorious.org. And posting a merge request to the ffmpeg-devel mailing
> list.
Please no. The patches themselves need to go to the mailing list. If these
tools can not do that, then they are not usable for this project.
On date Saturday 2015-09-12 15:56:34 +0200, Michael Niedermayer encoded:
> From: Michael Niedermayer
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/developer.texi |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index b82
On date Monday 2015-09-07 11:37:47 +0200, Stefano Sabatini encoded:
> Hi,
>
> I propose to have an official IRC meeting on the next Saturday, and I
> propose the tentative time of 15:00 UTC, but feel free to propose a
> different time if this can't suit you.
>
> The IRC meeting channel will be pu
From: Michael Niedermayer
Signed-off-by: Michael Niedermayer
---
doc/developer.texi |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/developer.texi b/doc/developer.texi
index b8259e7..a3f2846 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -38,7 +38,7 @@ Th
Le sextidi 26 fructidor, an CCXXIII, Michael Niedermayer a écrit :
> If we depend on these developers/contributors then IMO we should take
> their oppinons and objections serious and if one of them is willing
> to risk her/his good name to oppose a proposal in public and maybe also
> plans to put s
Hi,
On Sat, Sep 12, 2015 at 9:39 AM, Hendrik Leppkes
wrote:
> On Sat, Sep 12, 2015 at 3:24 PM, Michael Niedermayer
> wrote:
> > On Sat, Sep 12, 2015 at 06:50:50AM -0400, Ronald S. Bultje wrote:
> >> Hi,
> >>
> >> On Sat, Sep 12, 2015 at 4:21 AM, Yayoi Ukai
> wrote:
> >>
> >> > On Thu, Sep 10,
On Sat, Sep 12, 2015 at 3:24 PM, Michael Niedermayer wrote:
> On Sat, Sep 12, 2015 at 06:50:50AM -0400, Ronald S. Bultje wrote:
>> Hi,
>>
>> On Sat, Sep 12, 2015 at 4:21 AM, Yayoi Ukai wrote:
>>
>> > On Thu, Sep 10, 2015 at 10:46 AM, Michael Niedermayer
>> > wrote:
>> > > On Mon, Sep 07, 2015 at
On Sat, Sep 12, 2015 at 06:50:50AM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Sat, Sep 12, 2015 at 4:21 AM, Yayoi Ukai wrote:
>
> > On Thu, Sep 10, 2015 at 10:46 AM, Michael Niedermayer
> > wrote:
> > > On Mon, Sep 07, 2015 at 11:37:47AM +0200, Stefano Sabatini wrote:
> > >> Hi,
> > >>
> > >>
On Sat, Sep 12, 2015 at 2:57 PM, Matt Oliver wrote:
> On 12 September 2015 at 19:40, Peter Belkner wrote:
>
>> On 12.09.2015 11:15, Geek.Song wrote:
>>
>>> diff -u
>>
>>
> LGTM.
> I had an identical patch ready to fix the same problem so this one is fine.
LGTM too, applied.
_
On 12 September 2015 at 19:40, Peter Belkner wrote:
> On 12.09.2015 11:15, Geek.Song wrote:
>
>> diff -u
>
>
LGTM.
I had an identical patch ready to fix the same problem so this one is fine.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://f
On Thu, Sep 10, 2015 at 04:43:42PM +0200, Tobias Rapp wrote:
> On 10.09.2015 15:28, Tobias Rapp wrote:
> >On 10.09.2015 14:57, Derek Buitenhuis wrote:
> >>On 9/10/2015 1:25 PM, Tobias Rapp wrote:
> >>>My use-case is handling recorded AVI files which have an
> >>>unknown/empty/unsupported channel la
Hi,
On Sat, Sep 12, 2015 at 4:21 AM, Yayoi Ukai wrote:
> On Thu, Sep 10, 2015 at 10:46 AM, Michael Niedermayer
> wrote:
> > On Mon, Sep 07, 2015 at 11:37:47AM +0200, Stefano Sabatini wrote:
> >> Hi,
> >>
> >> I propose to have an official IRC meeting on the next Saturday, and I
> >> propose the
On 12.09.2015 11:15, Geek.Song wrote:
diff -u
--- ./a/ffmpeg/configure2015-09-11 19:20:03.0 +0200
+++ ./b/ffmpeg/configure2015-09-12 11:36:32.78060 +0200
@@ -3297,7 +3297,7 @@
exesuf() {
case $1 in
-mingw32*|win32|win64|cygwin*|*-dos|freedos|opendos|o
On Sat, Sep 12, 2015 at 5:06 PM, Peter Belkner wrote:
> Hi,
>
> building current FFmpeg breaks on MSYS2 MINGW64
> (http://sourceforge.net/projects/msys2/) with error "Unknown OS
> 'mingw64_nt-6.0'." from "configure".
>
> Probably "mingw64_nt-6.0" results from "uname -s" on MSYS2 MINGW64:
>
>$
Hi,
building current FFmpeg breaks on MSYS2 MINGW64
(http://sourceforge.net/projects/msys2/) with error "Unknown OS
'mingw64_nt-6.0'." from "configure".
Probably "mingw64_nt-6.0" results from "uname -s" on MSYS2 MINGW64:
$ uname -s
MINGW64_NT-6.0
The attached patch seems to fix it.
R
FYI: Here is my experience with Python.org
Step 1: If it the decision is not so important (simple patch etc.) and
if 3 reviewers say yes, it will be merged.
Also, it seems there are no maintainers for specific parts of the
code, but instead they have "reviewers" and only
reviewers can review the p
On Thu, Sep 10, 2015 at 10:46 AM, Michael Niedermayer wrote:
> On Mon, Sep 07, 2015 at 11:37:47AM +0200, Stefano Sabatini wrote:
>> Hi,
>>
>> I propose to have an official IRC meeting on the next Saturday, and I
>> propose the tentative time of 15:00 UTC, but feel free to propose a
>> different ti
57 matches
Mail list logo