Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kyle Swanson <k@ylo.ph>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
Date: Wed, 21 May 2025 13:11:04 -0700
Message-ID: <CALbjROLnug1X8k2GL0NuHvr3NtCWZ2y2o1yr5zv4VXy6-ZmKKg@mail.gmail.com> (raw)
In-Reply-To: <CABGuwEkXQCKSKV9OPxCG0CoCHT2ALNpY+QBY=windK1_ZNtgvg@mail.gmail.com>

Hi,

On Wed, May 21, 2025 at 4:00 AM Kieran Kunhya via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
> Can we just revert the whole set until it's cleaned up properly?
>
> There are more patches to fix issues than the set itself. This is
> understandable if it's a bit architectural change like threading but it's
> not.

I agree with Kieran, revert. This was not ready to be pushed IMO.

Thanks,
Kyle
_______________________________________________
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".

  parent reply	other threads:[~2025-05-21 20:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  0:45 softworkz .
2025-05-21 10:59 ` Kieran Kunhya via ffmpeg-devel
2025-05-21 20:05   ` softworkz .
2025-05-21 20:11   ` Kyle Swanson [this message]
2025-05-21 20:19     ` softworkz .
2025-05-21 20:37       ` softworkz .
2025-05-22  7:21         ` Kieran Kunhya via ffmpeg-devel
2025-05-22  8:13           ` softworkz .
2025-05-22  9:28             ` softworkz .
2025-05-22  8:50           ` Nicolas George
2025-05-22  8:53             ` softworkz .
2025-05-22  8:56             ` softworkz .
2025-05-31 21:38             ` softworkz .
2025-05-22 11:23           ` Michael Niedermayer
2025-05-22 12:13             ` softworkz .
2025-05-22 12:46               ` Kieran Kunhya via ffmpeg-devel
2025-05-22 14:03                 ` softworkz .
2025-05-22 14:07                   ` Kieran Kunhya via ffmpeg-devel
2025-05-22 14:13                     ` softworkz .
2025-05-22 14:57                       ` softworkz .
2025-05-31 21:38                     ` softworkz .
2025-05-31 21:38                 ` softworkz .
2025-05-22 12:44             ` Kieran Kunhya via ffmpeg-devel

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=CALbjROLnug1X8k2GL0NuHvr3NtCWZ2y2o1yr5zv4VXy6-ZmKKg@mail.gmail.com \
    --to=k@ylo.ph \
    --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