Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 6.0
Date: Fri, 17 Feb 2023 04:50:10 +0100 (CET)
Message-ID: <NOSUaQD--B-9@lynne.ee> (raw)
In-Reply-To: <20230215231424.GA1949656@pb2>

Feb 16, 2023, 00:14 by michael@niedermayer.cc:

> On Fri, Feb 10, 2023 at 07:50:29PM +0100, Lynne wrote:
>
>> Feb 10, 2023, 18:47 by michael@niedermayer.cc:
>>
>> > Hi all
>> >
>> > i plan to branch off release/6.0 from master in the next days 
>> > If theres something blocking and i should wait, please reply here
>> >
>> > 6.0 release will be maybe 1 week after the branch point
>> > once it has branched all important fixes should be backported of course
>> >
>>
>> Working hard on the Vulkan rewrite with video decoding, finished
>> the infra today, just need to port all filters to it. I should be done
>> in a couple of days, so please wait for it.
>>
>
> Please reply here when its no longer blocking branching
>

Just submitted my patchset for review.
Once I get some reviews, will try to decide what can be fixed
now or during the testing period with backporting so I don't
hold the branching off too long.
I'll ping this thread once it's merged so you can branch.

Thanks for waiting for it
_______________________________________________
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:[~2023-02-17  3:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 17:47 Michael Niedermayer
2023-02-10 18:50 ` Lynne
2023-02-15 23:14   ` Michael Niedermayer
2023-02-17  3:50     ` Lynne [this message]
2023-02-11  5:44 ` Anton Khirnov
2023-02-21 11:38 ` Michael Niedermayer
2023-02-21 11:49   ` Paul B Mahol
2023-02-21 12:12   ` Gijs Peskens
2023-02-21 12:31     ` Reto Kromer
2023-02-21 12:31   ` Kieran Kunhya
2023-02-21 12:48     ` RADSL
2023-02-22 17:51       ` Michael Niedermayer
2023-02-21 13:20   ` Jean-Baptiste Kempf
2023-02-21 15:58     ` Michael Niedermayer
2023-02-24  4:01       ` Gyan Doshi
2023-02-25 12:58         ` Michael Niedermayer
2023-02-24 15:56   ` Niklas Haas
2023-02-24 16:40     ` Brad Isbell
2023-02-26 16:45   ` Michael Niedermayer
2023-02-26 13:18 ` Michael Niedermayer
2023-02-27  1:32   ` Wang Bin

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=NOSUaQD--B-9@lynne.ee \
    --to=dev@lynne.ee \
    --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