Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Rick Kern <kernrj@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3] avcodec/videotoolboxenc: Add CBR option to H264 and HEVC encoder
Date: Mon, 29 Aug 2022 09:36:48 -0400
Message-ID: <CABmg8gVzz4nv7=ENj0M4LpV8LWuvLYojV7SmtFUB8VFSwtg7Gw@mail.gmail.com> (raw)
In-Reply-To: <E0036FA9-0038-455E-B9A3-B2FEF1092785@outlook.de>

On Mon, Aug 29, 2022 at 9:05 AM Sebastian Beckmann <
beckmann.sebastian@outlook.de> wrote:

>
> > The patch doesn't apply. Can you create a .patch file with git
> format-patch
> > and send the file as an attachment? Sometimes email clients/providers
> > corrupt inline patches.
>

Thanks, pushed.


>
> _______________________________________________
> 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:[~2022-08-29 13:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 11:42 [FFmpeg-devel] [PATCH] " Sebastian Beckmann
2022-08-26 11:45 ` Diederick C. Niehorster
2022-08-26 12:34   ` [FFmpeg-devel] [PATCH v2] " Sebastian Beckmann
2022-08-28 18:37 ` [FFmpeg-devel] [PATCH] " Rick Kern
2022-08-28 20:27   ` [FFmpeg-devel] [PATCH v3] " Sebastian Beckmann
2022-08-29 12:58     ` Rick Kern
2022-08-29 13:04       ` Sebastian Beckmann
2022-08-29 13:36         ` Rick Kern [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='CABmg8gVzz4nv7=ENj0M4LpV8LWuvLYojV7SmtFUB8VFSwtg7Gw@mail.gmail.com' \
    --to=kernrj@gmail.com \
    --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