Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] RELEASE_NOTES: Based on the version from 5.0
Date: Mon, 18 Jul 2022 13:39:47 +0200
Message-ID: <165814438789.25016.3088462541923995798@lain.khirnov.net> (raw)
In-Reply-To: <20220717142340.GN2088045@pb2>

Quoting Michael Niedermayer (2022-07-17 16:23:40)
> On Sun, Jul 17, 2022 at 10:43:02AM +0200, Jean-Baptiste Kempf wrote:
> > Maybe some highlights of this release? Like the biggest changes and improvements?
> 
> Isnt that what Changelog is already doing ?

By tradition, only certain things get mentioned in Changelog, like new
codecs/(de)muxers/filters and such. Things like API changes, performance
improvements, or other significant changes that are not one of the
above, do not get mentioned. We might want to change that.

-- 
Anton Khirnov
_______________________________________________
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:[~2022-07-18 11:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 15:09 Michael Niedermayer
2022-07-16 20:05 ` Martijn van Beurden
2022-07-16 20:35   ` Michael Niedermayer
2022-07-16 21:02     ` Martijn van Beurden
2022-07-16 22:50       ` Michael Niedermayer
2022-07-17  8:01         ` Martijn van Beurden
2022-07-20 15:28           ` Michael Niedermayer
2022-07-17  8:43 ` Jean-Baptiste Kempf
2022-07-17 14:23   ` Michael Niedermayer
2022-07-18 11:39     ` Anton Khirnov [this message]
2022-07-18 16:20       ` 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=165814438789.25016.3088462541923995798@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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