From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] doc/ffprobe: clarify that the input file is not optional
Date: Thu, 21 Apr 2022 10:17:04 +0530
Message-ID: <403c8fcb-cd15-5f1c-af73-a7a9a52a579f@gyani.pro> (raw)
In-Reply-To: <20220420214346.50037-1-stefasab@gmail.com>
Will apply.
On 2022-04-21 03:13 am, Stefano Sabatini wrote:
> Fix trac issue http://trac.ffmpeg.org/ticket/9562
> ---
> doc/ffprobe.texi | 2 +-
> fftools/ffprobe.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/ffprobe.texi b/doc/ffprobe.texi
> index 59a397a225..c61b8979b1 100644
> --- a/doc/ffprobe.texi
> +++ b/doc/ffprobe.texi
> @@ -12,7 +12,7 @@
>
> @chapter Synopsis
>
> -ffprobe [@var{options}] [@file{input_url}]
> +ffprobe [@var{options}] @file{input_url}
>
> @chapter Description
> @c man begin DESCRIPTION
> diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
> index 05c167eeb5..c51c82ff65 100644
> --- a/fftools/ffprobe.c
> +++ b/fftools/ffprobe.c
> @@ -3417,7 +3417,7 @@ end:
> static void show_usage(void)
> {
> av_log(NULL, AV_LOG_INFO, "Simple multimedia streams analyzer\n");
> - av_log(NULL, AV_LOG_INFO, "usage: %s [OPTIONS] [INPUT_FILE]\n", program_name);
> + av_log(NULL, AV_LOG_INFO, "usage: %s [OPTIONS] INPUT_FILE\n", program_name);
> av_log(NULL, AV_LOG_INFO, "\n");
> }
>
_______________________________________________
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:[~2022-04-21 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 21:43 Stefano Sabatini
2022-04-21 4:47 ` Gyan Doshi [this message]
2022-04-21 7:06 ` Gyan Doshi
2022-06-12 10:42 ` Stefano Sabatini
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=403c8fcb-cd15-5f1c-af73-a7a9a52a579f@gyani.pro \
--to=ffmpeg@gyani.pro \
--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