From: Marth64 <marth64@proxyid.net>
To: Marth64 <marth64@proxyid.net>
Cc: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/filter: fix typos in introduction with the word 'unlabelled'
Date: Wed, 3 Jan 2024 16:53:34 -0600
Message-ID: <CA+28BfCZ-fXb2_7yDKo3-OqbGr1-Fif=ckqAKkaOt2A8fLgO6Q@mail.gmail.com> (raw)
In-Reply-To: <20240103225135.1202052-1-marth64@proxyid.net>
Kindly disregard. This is not actually a typo, it is valid regional
English. Sorry. Just ignore this one.
On Wed, Jan 3, 2024 at 4:51 PM Marth64 <marth64@proxyid.net> wrote:
> Signed-off-by: Marth64 <marth64@proxyid.net>
> ---
> doc/filters.texi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/filters.texi b/doc/filters.texi
> index f4084ff494..eff2256fef 100644
> --- a/doc/filters.texi
> +++ b/doc/filters.texi
> @@ -195,7 +195,7 @@ filtergraph, a link between the corresponding input
> and output pad is
> created.
>
> If an output pad is not labelled, it is linked by default to the first
> -unlabelled input pad of the next filter in the filterchain.
> +unlabeled input pad of the next filter in the filterchain.
> For example in the filterchain
> @example
> nullsrc, split[L1], [L2]overlay, nullsink
> @@ -204,13 +204,13 @@ the split filter instance has two output pads, and
> the overlay filter
> instance two input pads. The first output pad of split is labelled
> "L1", the first input pad of overlay is labelled "L2", and the second
> output pad of split is linked to the second input pad of overlay,
> -which are both unlabelled.
> +which are both unlabeled.
>
> In a filter description, if the input label of the first filter is not
> specified, "in" is assumed; if the output label of the last filter is not
> specified, "out" is assumed.
>
> -In a complete filterchain all the unlabelled filter input and output
> +In a complete filterchain all the unlabeled filter input and output
> pads must be connected. A filtergraph is considered valid if all the
> filter input and output pads of all the filterchains are connected.
>
> --
> 2.34.1
>
>
_______________________________________________
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".
prev parent reply other threads:[~2024-01-03 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 22:51 Marth64
2024-01-03 22:53 ` Marth64 [this message]
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='CA+28BfCZ-fXb2_7yDKo3-OqbGr1-Fif=ckqAKkaOt2A8fLgO6Q@mail.gmail.com' \
--to=marth64@proxyid.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