Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/APIchanges: add missing marker for release 5.0
Date: Thu, 16 Jun 2022 12:55:56 +0530
Message-ID: <306c2f27-3798-68da-0095-cc909dfeb039@gyani.pro> (raw)
In-Reply-To: <d413585e-5cc7-bc84-0c29-6554b4533be2@gyani.pro>



On 2022-06-15 01:49 pm, Gyan Doshi wrote:
> Will push later today.

Pushed as 557a1a8af27a2666433ca9970a15addcd1d8a506



>
> On 2022-06-14 03:11 pm, Gyan Doshi wrote:
>> ---
>>   doc/APIchanges | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/doc/APIchanges b/doc/APIchanges
>> index 5857e67ae6..20b944933a 100644
>> --- a/doc/APIchanges
>> +++ b/doc/APIchanges
>> @@ -96,6 +96,8 @@ API changes, most recent first:
>>   2022-01-26 - af94ab7c7c0 - lavu 57.19.100 - tx.h
>>     Add AV_TX_FLOAT_RDFT, AV_TX_DOUBLE_RDFT and AV_TX_INT32_RDFT.
>>   +-------- 8< --------- FFmpeg 5.0 was cut here -------- 8< ---------
>> +
>>   2022-01-04 - 78dc21b123e - lavu 57.16.100 - frame.h
>>     Add AV_FRAME_DATA_DOVI_METADATA.
>
> _______________________________________________
> 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".

_______________________________________________
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-06-16  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  9:41 Gyan Doshi
2022-06-15  8:19 ` Gyan Doshi
2022-06-16  7:25   ` Gyan Doshi [this message]

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=306c2f27-3798-68da-0095-cc909dfeb039@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --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