Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/filters: add missing anchors
Date: Thu, 28 Sep 2023 00:58:58 +0200 (CEST)
Message-ID: <be8579e-62d2-e216-f536-23b1eb79f11c@passwd.hu> (raw)
In-Reply-To: <20230927225159.2305-1-jamrial@gmail.com>



On Wed, 27 Sep 2023, James Almer wrote:

> Fixes build failures introduced in 7f685d0f49.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> doc/filters.texi | 2 ++
> 1 file changed, 2 insertions(+)

LGTM, thanks.

Marton

>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index c25450cf6c..a729a08dce 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -16837,6 +16837,7 @@ ffmpeg -init_hw_device vulkan -hwaccel vaapi -hwaccel_output_format vaapi ... -v
> @end example
> @end itemize
>
> +@anchor{libvmaf}
> @section libvmaf
>
> Calulate the VMAF (Video Multi-Method Assessment Fusion) score for a
> @@ -20895,6 +20896,7 @@ If the specified expression is not valid, it is kept at its current
> value.
> @end table
>
> +@anchor{scale_cuda}
> @section scale_cuda
>
> Scale (resize) and convert (pixel format) the input video, using accelerated CUDA kernels.
> -- 
> 2.42.0
>
> _______________________________________________
> 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".
>
_______________________________________________
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".

  reply	other threads:[~2023-09-27 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 22:51 James Almer
2023-09-27 22:58 ` Marton Balint [this message]
2023-09-27 23:43   ` James Almer

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=be8579e-62d2-e216-f536-23b1eb79f11c@passwd.hu \
    --to=cus@passwd.hu \
    --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