Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libx264: bump minimum required version to 160
Date: Thu, 11 Apr 2024 12:01:56 +0200
Message-ID: <Zhe1FOskVsj7tERB@phare.normalesup.org> (raw)
In-Reply-To: <20240410231725.GT6420@pb2>

Michael Niedermayer (12024-04-11):
> Maybe its just me but i find it desireable to be able to just
> pull ffmpeg master head, build it and have it work on as many systems
> as possible.

Not just you. The last time x264 had a change that would make me install
from sources instead of using an older package was 2017, build 152.
While the last time FFmpeg added features… is not that recent since
features are more being removed these days, but still recent enough.

Regards,

-- 
  Nicolas George
_______________________________________________
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".

  reply	other threads:[~2024-04-11 10:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 17:44 Niklas Haas
2024-04-06 20:28 ` Michael Niedermayer
2024-04-09 12:53   ` Niklas Haas
2024-04-10 13:18     ` Michael Niedermayer
2024-04-10 13:30       ` Hendrik Leppkes
2024-04-10 23:17         ` Michael Niedermayer
2024-04-11 10:01           ` Nicolas George [this message]
2024-04-11 21:05             ` Vittorio Giovara
2024-04-10 13:47       ` Niklas Haas
2024-04-10 23:32         ` Michael Niedermayer
2024-04-11 22:55           ` Sean McGovern
2024-04-12 10:43             ` Tomas Härdin
2024-04-12 11:45             ` 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=Zhe1FOskVsj7tERB@phare.normalesup.org \
    --to=george@nsup.org \
    --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