From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] FFmpeg 5.0
Date: Fri, 28 Oct 2022 20:23:33 +0200
Message-ID: <20221028182333.GJ4048598@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 466 bytes --]
Hi
According to our
https://trac.ffmpeg.org/wiki/Downstreams
Noone and nothing is using 5.0
should i make another release of 5.0 ?
should i move 5.0 to olddownloads ?
does anyone use it ? plan to use it or know of someone using it ?
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
[-- 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 reply other threads:[~2022-10-28 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 18:23 Michael Niedermayer [this message]
2022-10-28 19:10 ` Timo Rothenpieler
2022-10-28 20:17 ` AV Preservation by reto.ch (lists)
2022-10-29 18:29 ` Neal Gompa
2022-10-29 19:42 ` Timo Rothenpieler
2022-10-30 20:10 ` Michael Niedermayer
2022-10-30 21:04 ` Neal Gompa
2022-10-31 13:03 ` Anton Khirnov
2022-10-31 17:51 ` Andreas Schneider
2022-11-03 22:23 ` Michael Niedermayer
2022-10-30 20:16 ` Michael Niedermayer
2022-10-30 20:53 ` Neal Gompa
[not found] ` <ss9225p7-9rpo-r229-5914-4n555p66sos@vanv.qr>
2022-10-31 14:33 ` Michael Niedermayer
2022-11-03 22:28 ` Michael Niedermayer
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=20221028182333.GJ4048598@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