From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavutil/log: Support for logging timestamps in the log
Date: Fri, 17 Feb 2023 12:07:47 +0100
Message-ID: <167663206793.1179.18261691439793810470@lain.khirnov.net> (raw)
In-Reply-To: <CAB1hn_zPeaFQeFPSvMpdLNTMZ5YG=sHhpQJwrsKmVaM=w4KUUg@mail.gmail.com>
Quoting Prakash (2023-02-17 01:16:04)
> Moved the timestamp to the front (before loglevel but after the prefix if
> present, so the timestamp has the same color as log line based on log
> level). Updated the patch and attached again.
>
>
> From 04857a7bf0d4cf24a479e795a55a61ab2e2f618e Mon Sep 17 00:00:00 2001
> From: Prakash Duggaraju <duggaraju@gmail.com>
> Date: Thu, 16 Feb 2023 16:06:29 -0800
> Subject: [PATCH] libavutil/log: Support for logging timestamps in the log.
> Add
> 'time' flag to the -loglevel option to turn on timestamp logging. Useful
> for
> troubleshooting where time is spent from the log files.
>
> Signed-off-by: Prakash Duggaraju <duggaraju@gmail.com>
> ---
> doc/fftools-common-opts.texi | 4 ++++
> fftools/opt_common.c | 6 ++++++
> libavutil/log.c | 41 +++++++++++++++++++++++++-----------
> libavutil/log.h | 8 +++++++
> 4 files changed, 47 insertions(+), 12 deletions(-)
I do not like this patch.
The default logging callback should be simple and straightforward, not a
kitchen sink of all possible functionality.
Callers who need this can and should implement this themselves.
--
Anton Khirnov
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-02-17 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 21:52 Prakash
2023-01-18 8:51 ` Tobias Rapp
2023-01-18 23:20 ` Prakash
2023-01-19 8:24 ` Tobias Rapp
2023-02-17 0:16 ` Prakash
2023-02-17 11:07 ` Anton Khirnov [this message]
2023-02-17 11:49 ` Lynne
2023-02-17 18:55 ` Prakash
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167663206793.1179.18261691439793810470@lain.khirnov.net \
--to=anton@khirnov.net \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git