From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 99/99] Vulkan patchset - complete
Date: Sun, 28 May 2023 05:16:01 +0200 (CEST)
Message-ID: <NWVLl5S--3-9@lynne.ee> (raw)
In-Reply-To: <NWVGWv4--3-9@lynne.ee-NWVGaUX----9>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
May 28, 2023, 04:53 by dev@lynne.ee:
> This contains the entire Vulkan patchset, 99 patches from 4 authors.
>
> Thanks to everyone who contributed code, reviewed code,
> voiced their opinions and tested the code over the past 6 months.
>
> Patchset attached (1.1 Mb uncompressed, too large for the ML).
>
Forgot to git add the FATE ref files for the new pixfmts and
to exclude apache-licensed files from fate-source, bringing
the total up to 100 patches.
[-- Attachment #2: vulkan_patchset.tar --]
[-- Type: application/x-tar, Size: 198160 bytes --]
[-- Attachment #3: 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 prev parent reply other threads:[~2023-05-28 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 20:35 [FFmpeg-devel] [PATCH] lavu/tx: stop using av_log(NULL, ) Lynne
2023-05-24 20:44 ` Paul B Mahol
2023-05-24 21:24 ` Leo Izen
2023-05-25 0:32 ` Lynne
2023-05-28 1:07 ` James Almer
2023-05-28 2:48 ` Lynne
2023-05-28 17:00 ` Anton Khirnov
2023-05-28 2:53 ` [FFmpeg-devel] [PATCH 99/99] Vulkan patchset - complete Lynne
[not found] ` <NWVGWv4--3-9@lynne.ee-NWVGaUX----9>
2023-05-28 3:16 ` Lynne [this message]
[not found] ` <NWVLl5S--3-9@lynne.ee-NWVLpfB----9>
2023-05-28 23:16 ` Lynne
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=NWVLl5S--3-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