From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 6.1.1
Date: Fri, 5 Jan 2024 22:24:56 +0100
Message-ID: <20240105212456.GF6420@pb2> (raw)
In-Reply-To: <4b1a7861-0381-337d-bb59-ab0777bb378a@softwolves.pp.se>
[-- Attachment #1.1: Type: text/plain, Size: 776 bytes --]
On Fri, Jan 05, 2024 at 09:15:37AM +0100, Peter Krefting wrote:
> Hi!
>
> > I will probably make a 6.1.1 release in maybe 1-3 weeks due to bug/fixes
> > in it.
> > if you want something in it, please backport it now!
>
> Any chance of getting the patch submitted in
> <https://ffmpeg.org/pipermail/ffmpeg-devel/2022-September/302148.html> into
> this or a subsequent release? I had to apply it manually when upgrading our
> build system to 6.1 recently.
This first needs to be applied to master before it can be put in a release.
Also can dcbzl be detected at runtime ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The educated differ from the uneducated as much as the living from the
dead. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-01-05 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 19:17 Michael Niedermayer
2023-12-28 9:13 ` yinshiyou-hf
2023-12-28 9:54 ` Zhao Zhili
2024-01-05 8:15 ` Peter Krefting
2024-01-05 21:24 ` Michael Niedermayer [this message]
2024-01-05 23:17 ` Romain Beauxis
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=20240105212456.GF6420@pb2 \
--to=michael@niedermayer.cc \
--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