From: "Diederick C. Niehorster" <dcnieho@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/5] avdevice/dshow fixups
Date: Tue, 4 Jan 2022 11:36:23 +0100
Message-ID: <CABcAi1gE0JpFFAZQhg1Tw9PwJDX6TD0qgXWoXMDfEXZ9ePNtAA@mail.gmail.com> (raw)
In-Reply-To: <c427050c-a223-d290-7ccc-ca046744c44b@gyani.pro>
On Tue, Jan 4, 2022 at 5:10 AM Gyan Doshi <ffmpeg@gyani.pro> wrote:
> On 2022-01-04 05:02 am, Roger Pack wrote:
> > These LGTM. Feel free to add yourself as a dshow maintainer if so
> > interested, as well! :)
>
> I assume these need to be pushed too.
Yes thanks, please push. Would be good to get in before the release
branch, fixing the regressions.
Thanks!
Dee
_______________________________________________
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".
next prev parent reply other threads:[~2022-01-04 10:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 9:49 Diederick Niehorster
2022-01-02 9:49 ` [FFmpeg-devel] [PATCH v2 1/5] avdevice/dshow: tv_tuner_audio_dialog cleanup missing Diederick Niehorster
2022-01-02 9:49 ` [FFmpeg-devel] [PATCH v2 2/5] avdevice/dshow: proper cleanup of queried media types Diederick Niehorster
2022-01-02 9:49 ` [FFmpeg-devel] [PATCH v2 3/5] avdevice/dshow: fix crash on x86 Diederick Niehorster
2022-01-02 9:49 ` [FFmpeg-devel] [PATCH v2 4/5] avdevice/dshow: only set pin format if wanted Diederick Niehorster
2022-01-02 9:49 ` [FFmpeg-devel] [PATCH v2 5/5] avdevice/dshow: ensure pin's default format is set Diederick Niehorster
2022-01-03 23:32 ` [FFmpeg-devel] [PATCH v2 0/5] avdevice/dshow fixups Roger Pack
2022-01-04 4:10 ` Gyan Doshi
2022-01-04 10:36 ` Diederick C. Niehorster [this message]
2022-01-04 12:05 ` Gyan Doshi
2022-01-04 16:28 ` Diederick C. Niehorster
2022-01-04 17:12 ` Gyan Doshi
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=CABcAi1gE0JpFFAZQhg1Tw9PwJDX6TD0qgXWoXMDfEXZ9ePNtAA@mail.gmail.com \
--to=dcnieho@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