Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/tls_mbedtls: Changes the return code handling of mbedtls_x509_crt_parse_file
Date: Wed, 17 Jul 2024 17:24:32 -0500
Message-ID: <CA+28BfCr2gV2t+OE4gKsc05DDwtqbZPKdr90FKW-ThVU4sFrhA@mail.gmail.com> (raw)
In-Reply-To: <CALpSoPWNwbvD8dQU3nA_DREDrqC=_gu8zHYhH7QLbiXKNr+UdQ@mail.gmail.com>

Disclaimer: I am a light contributor and do not have access
to actually merge this patch, only making suggestions based
on my learnings.

> Sounds good. Sorry first time contributing, should I make another patch
> with the change and send that through again with git send-email?
Yes, except when you do git format-patch, specify "-v2" at the end
and provide the message ID of your original email, so it processes as a reply.

This will prefix the patch subject with "V2" to let readers know you have
updated it.

Thank you!
_______________________________________________
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:[~2024-07-17 22:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 13:25 Mohit Gupta
2024-07-14 16:26 ` Marth64
2024-07-14 16:29   ` Marth64
2024-07-16  0:56     ` Mohit Gupta
2024-07-16  1:25       ` Marth64
2024-07-16 19:20         ` Mohit Gupta
2024-07-17 22:24           ` Marth64 [this message]
2024-07-25  0:32             ` [FFmpeg-devel] [PATCH v2] " Mohit Gupta
2024-08-01  4:50               ` Marth64
2024-08-01 17:05                 ` Mohit Gupta
2024-08-01 17:34                   ` [FFmpeg-devel] [PATCH v3] " Mohit Gupta

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+28BfCr2gV2t+OE4gKsc05DDwtqbZPKdr90FKW-ThVU4sFrhA@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