From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [RFC] Anyone using 6.0, 4.1, 3.4 ? Date: Mon, 15 Apr 2024 01:55:42 +0200 Message-ID: <20240414235542.GC6420@pb2> (raw) [-- Attachment #1.1: Type: text/plain, Size: 979 bytes --] Hi I see nothing using 6.0 and 4.1 on our downstreams page, so i suggest to move 6.0 to the archieve page after 6.0.2 and 4.1 probably without new releases About 3.4 ubuntu 18.04 last updated its FFmpeg 3.4 package 15 November 2023 sadly "apt changelog" doesnt seem to work with that package so iam not sure that includes our fixes or only other things our last 3.4 release was 2023-06-12 but i intend to make new 3.4 and 2.8 releases too The branches can be droped afterwards if noone is left using these. But as shown above ubuntu is still actively doing things with these packages so if someone confirms that ubuntu still has interrest in these (or another distro) then ill try to continue to update these thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Take away the freedom of one citizen and you will be jailed, take away the freedom of all citizens and you will be congratulated by your peers in Parliament. [-- 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:[~2024-04-14 23:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-14 23:55 Michael Niedermayer [this message] 2024-04-15 0:15 ` James Almer 2024-04-15 8:07 ` Michael Niedermayer 2024-04-17 1:27 ` James Almer 2024-04-15 7:38 ` Jean-Baptiste Kempf
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=20240414235542.GC6420@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