On Mon, Mar 30, 2015 at 5:19 PM, Nicolas George geo...@nsup.org wrote:
Le nonidi 9 germinal, an CCXXIII, Stephan Holljes a écrit :
I hope this addresses the issues mentioned.
I added a new label in case of failure in http_open() in favor of
duplicated code (i.e. calling av_dict_free() multiple
Le nonidi 9 germinal, an CCXXIII, Stephan Holljes a écrit :
I hope this addresses the issues mentioned.
I added a new label in case of failure in http_open() in favor of
duplicated code (i.e. calling av_dict_free() multiple times). I copied
the style from the other functions.
Signed-off-by:
On Sun, 29 Mar 2015 04:13:18 +0200
Stephan Holljes klaxa1...@googlemail.com wrote:
I hope this addresses the issues mentioned.
I added a new label in case of failure in http_open() in favor of
duplicated code (i.e. calling av_dict_free() multiple times). I copied
the style from the other
I hope this addresses the issues mentioned.
I added a new label in case of failure in http_open() in favor of
duplicated code (i.e. calling av_dict_free() multiple times). I copied
the style from the other functions.
Signed-off-by: Stephan Holljes klaxa1...@googlemail.com
---
doc/protocols.texi
I hope this time the patch is formatted correctly. I also attached it
in case it is corrupted again.
I changed the indentation of the code and used ffurl_open() instead of
creating my own listening socket.
I am still having some trouble with the Content-Type header. I would
guess creating
Le primidi 1er germinal, an CCXXIII, Stephan Holljes a écrit :
Please comment.
As Michael pointed out, the patch was mangled at sending. That happens with
mail user agent that rely on rich text editor and do not let users control
the formatting finely. Using git send-email or attaching the file
Hi,
what would be the correct way to create patches that won't be corrupted? I
merely tried to copy what I have seen on the mailing-list before,
apparently I didn't do a very good job ;)
Regards,
Stephan Holljes
On Sun, Mar 22, 2015 at 12:24 AM, Michael Niedermayer michae...@gmx.at
wrote:
On
On Sun, Mar 22, 2015 at 12:33:57AM +0100, Stephan Holljes wrote:
Hi,
what would be the correct way to create patches that won't be corrupted? I
merely tried to copy what I have seen on the mailing-list before,
apparently I didn't do a very good job ;)
git send-email -1
would send the most
On Sun, Mar 22, 2015 at 2:34 AM, Michael Niedermayer michae...@gmx.at
wrote:
On Sun, Mar 22, 2015 at 12:33:57AM +0100, Stephan Holljes wrote:
Hi,
what would be the correct way to create patches that won't be corrupted?
I
merely tried to copy what I have seen on the mailing-list before,
