From: sfan5 <sfan5@live.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/6] lavf/tls_mbedtls: handle more error codes for human-readable message
Date: Tue, 21 May 2024 12:08:44 +0200
Message-ID: <DU0PR03MB95678F0585D5C286195F0004ECEA2@DU0PR03MB9567.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <ZkcmohUlfXwf3wzc@andrews-2024-laptop.sayers>
Am 17.05.24 um 11:42 schrieb Andrew Sayers:
> On Fri, May 17, 2024 at 10:34:26AM +0200, Sfan5 wrote:
>> Signed-off-by: sfan5 <sfan5@live.de>
>> ---
>> libavformat/tls_mbedtls.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/libavformat/tls_mbedtls.c b/libavformat/tls_mbedtls.c
>> index 1a182e735e..fd6ba0b1f5 100644
>> --- a/libavformat/tls_mbedtls.c
>> +++ b/libavformat/tls_mbedtls.c
>> @@ -138,6 +138,9 @@ static void handle_handshake_error(URLContext *h, int
>> ret)
>> case MBEDTLS_ERR_SSL_HANDSHAKE_FAILURE:
>> av_log(h, AV_LOG_ERROR, "TLS handshake failed.\n");
>> break;
>> + case MBEDTLS_ERR_SSL_BAD_PROTOCOL_VERSION:
>> + av_log(h, AV_LOG_ERROR, "TLS protocol version mismatches.\n");
> "... mismatch" or "... does not match" would be more readable than "mismatches".
>
> The word "matches" can mean either "does match" or "plural of match".
> It's technically valid to use "mismatches" to mean "does not match",
> but in practice the word is only ever used to mean "plural of mismatch".
Alright. Will change for v2.
_______________________________________________
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-05-21 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 8:34 Sfan5
2024-05-17 9:42 ` Andrew Sayers
2024-05-21 10:08 ` sfan5 [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=DU0PR03MB95678F0585D5C286195F0004ECEA2@DU0PR03MB9567.eurprd03.prod.outlook.com \
--to=sfan5@live.de \
--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