On 4/27/2016 7:22 PM, Michael Niedermayer wrote:
>
> applied both patches
>
> thx
>
Thank you for the review.
Best regards,
Andreas
signature.asc
Description: OpenPGP digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://f
From: Andreas Weis
The new function behaves the same as av_log_format_line, but also forwards
the return value from the underlying snprintf call. This will allow
callers to accurately determine the size requirements for the line buffer.
Signed-off-by: Andreas Weis
---
doc/APIchanges | 4
From: Andreas Weis
Signed-off-by: Andreas Weis
---
libavutil/log.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/libavutil/log.c b/libavutil/log.c
index 0efba7a..7e279ad 100644
--- a/libavutil/log.c
+++ b/libavutil/log.c
@@ -444,6 +444,17 @@ void
From: Andreas Weis
---
libavutil/log.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/libavutil/log.c b/libavutil/log.c
index 0efba7a..6d192b6 100644
--- a/libavutil/log.c
+++ b/libavutil/log.c
@@ -444,6 +444,17 @@ void avpriv_report_missing_feature(void
From: Andreas Weis
The new function behaves the same as av_log_format_line, but also forwards
the return value from the underlying snprintf call. This will allow
callers to accurately determine the size requirements for the line buffer.
---
doc/APIchanges | 4
libavutil/log.c
On 4/21/2016 10:31 AM, Hendrik Leppkes wrote:
> You can change the git configuration on a per-project basis, no need
> to change it on a global scale.
The stronger case here is in my opinion anyway the fact that this is not
something the user should have to worry about at all, especially if they
j
compile on a fresh Windows
checkout with autocrlf=true. It might be desirable to enable the same
behavior for other build script files like configure.
Thanks & regards,
Andreas
From 0d32c2105dc17be4de6aa1c76947d7baef62a5ba Mon Sep 17 00:00:00 2001
From: Andreas Weis
Date: Thu, 21 Apr 2016 0
>> I was trying to use a custom log callback and noticed that this pretty
>> much requires using av_log_format_line(), as the interpretation of the
>> format string is not trivial.
>
> Uh what? It's just snprintf formatting. What av_log_format_line() is
> adding additional information, which in th
Hi everyone!
I was trying to use a custom log callback and noticed that this pretty
much requires using av_log_format_line(), as the interpretation of the
format string is not trivial.
Unfortunately this approach offers no way of determining the size of the
output buffer for the log message. Typi
