From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] configure: stop allowing disabling lzo
Date: Sat, 26 Feb 2022 14:24:43 -0300
Message-ID: <a6bb973e-2a1a-e748-192b-0c0b26ecd9a0@gmail.com> (raw)
In-Reply-To: <22902316-F967-4EC3-B998-725E4863A53E@gmx.de>
On 2/26/2022 1:46 PM, Reimar Döffinger wrote:
>
>> On 26 Feb 2022, at 16:33, James Almer <jamrial@gmail.com> wrote:
>>
>> The module is now always compiled in.
>
> Thanks, both patches in this series or the alternative patch are fine with me.
> Only possible downside I could think of is if there is any use-case why someone would want the matroska decoder to specifically NOT have LZO support.
>
Applied then, thanks.
> Best regards,
> Reimar
>
> P.S.: If it's not too much effort I do appreciate a CC on patches for things where I am mentioned in MAINTAINERS as the list is a bit high-traffic for me
> _______________________________________________
> 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".
prev parent reply other threads:[~2022-02-26 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 15:33 [FFmpeg-devel] [PATCH 1/2 v2] avutil: make lzo always compile James Almer
2022-02-26 15:33 ` [FFmpeg-devel] [PATCH 2/2] configure: stop allowing disabling lzo James Almer
2022-02-26 16:46 ` Reimar Döffinger
2022-02-26 17:24 ` James Almer [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=a6bb973e-2a1a-e748-192b-0c0b26ecd9a0@gmail.com \
--to=jamrial@gmail.com \
--cc=Reimar.Doeffinger@gmx.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