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] [PATCH 55/97] Vulkan patchset part 2 - hwcontext rewrite and filtering
Date: Thu, 11 May 2023 19:16:20 +0200 (CEST)
Message-ID: <NVAo3i2--3-9@lynne.ee> (raw)
In-Reply-To: <168382287659.3843.9198132972211407440@lain.khirnov.net>

May 11, 2023, 18:34 by anton@khirnov.net:

> Quoting Lynne (2023-04-24 17:56:38)
>
>> From 89e47afc304aaf01c9c25a328ddfde37873e1f89 Mon Sep 17 00:00:00 2001
>> From: Lynne <dev@lynne.ee>
>> Date: Wed, 11 Jan 2023 09:37:35 +0100
>> Subject: [PATCH 59/97] hwcontext_vulkan: rewrite to support multiplane
>>  surfaces
>>
>> ---
>>  libavutil/hwcontext_vulkan.c | 791 +++++++++++++++++++----------------
>>  libavutil/hwcontext_vulkan.h |  73 ++--
>>  2 files changed, 474 insertions(+), 390 deletions(-)
>>
>
> Again, lol. Not to menion an ABI break.
>

I admit, it's an ABI break as it adds fields introduced before
a few commits prior in the same patch series.
But given that the patchset as a whole does not break the
ABI, I'd like to keep this, as the order is more appropriate,
and swapping the order of the two commits is impossible
without squashing literally every single commit in between
into a giant patch whose commit message starts with a re-
word.
_______________________________________________
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-05-11 17:16 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 15:56 Lynne
2023-04-28 13:28 ` Niklas Haas
     [not found] ` <NTnyn9K--3-9@lynne.ee-NTnytIf----9>
2023-05-10 19:10   ` Lynne
2023-05-11 15:36 ` Anton Khirnov
2023-05-11 16:32   ` Lynne
2023-05-11 16:59     ` Anton Khirnov
2023-05-11 16:03 ` Anton Khirnov
2023-05-11 18:55   ` Lynne
2023-05-16 13:31     ` Anton Khirnov
2023-05-16 14:47       ` Lynne
     [not found]       ` <NV_0sN0--3-9@lynne.ee-NV_0vMs----9>
2023-05-22  8:26         ` Lynne
     [not found]         ` <NVyq4UQ--F-9@lynne.ee-NW1ZGRp----9>
2023-05-25  0:31           ` Lynne
     [not found]           ` <NWFJK4e--3-9@lynne.ee-NWFJONn----9>
2023-05-26 17:52             ` Lynne
2023-05-26 19:19               ` Anton Khirnov
2023-05-26 20:50                 ` Lynne
2023-05-11 16:05 ` Anton Khirnov
2023-05-11 16:40   ` Lynne
2023-05-11 17:00     ` Anton Khirnov
2023-05-11 16:06 ` Anton Khirnov
2023-05-11 16:45   ` Lynne
2023-05-11 16:14 ` Anton Khirnov
2023-05-11 16:47   ` Lynne
2023-05-11 17:13     ` Anton Khirnov
2023-05-11 16:15 ` Anton Khirnov
2023-05-11 16:50   ` Lynne
2023-05-11 16:21 ` Anton Khirnov
2023-05-11 18:58   ` Lynne
2023-05-16 13:33     ` Anton Khirnov
2023-05-16 14:41       ` Lynne
2023-05-11 16:29 ` Anton Khirnov
2023-05-11 18:13   ` Lynne
2023-05-16 13:40     ` Anton Khirnov
2023-05-16 14:46       ` Lynne
2023-05-18  8:29         ` Anton Khirnov
2023-05-18 12:28           ` Lynne
2023-05-11 16:34 ` Anton Khirnov
2023-05-11 17:12   ` Lynne
2023-05-11 17:19     ` Anton Khirnov
2023-05-11 16:34 ` Anton Khirnov
2023-05-11 17:16   ` Lynne [this message]
2023-05-11 16:40 ` Anton Khirnov
2023-05-11 17:20   ` Lynne
2023-05-11 17:27     ` Anton Khirnov
2023-05-11 19:11       ` Lynne
2023-05-18  8:34 ` [FFmpeg-devel] libavcodec: add Vulkan common video code Anton Khirnov
2023-05-18 11:07   ` Lynne
2023-05-18  8:54 ` [FFmpeg-devel] libavcodec: add Vulkan common video decoding code Anton Khirnov
2023-05-18 12:27   ` Lynne
2023-05-19 12:11 ` [FFmpeg-devel] [PATCH 55/97] Vulkan patchset part 2 - hwcontext rewrite and filtering Leo Izen

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=NVAo3i2--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