Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
Date: Wed, 21 May 2025 11:59:49 +0100
Message-ID: <CABGuwEkXQCKSKV9OPxCG0CoCHT2ALNpY+QBY=windK1_ZNtgvg@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB036557FE6BF9356FA16030F3BA9EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Wed, 21 May 2025, 01:45 softworkz ., <softworkz-at-hotmail.com@ffmpeg.org>
wrote:

> Hello,
>
> thanks again to all for the patches. I figured it might be a bit difficult
> to
> keep track of what has already been submitted and fixed and is still
> pending, and I'm sorry that there has been some duplicate effort to fix the
> same things - so here's an overview. The ones with X are the ones I would
> like to apply eventually:
>
>
> Timo Rothenpieler
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14528
> (I would favor "ffbuild/commonmak" over for 1/3)
>
>   [1/3] fftools/resources: fix preservation of intermediary resman build
> artifacts
> X [2/3] ffbuild: correctly silence and tag new css/html steps
> X [3/3] fftools/resources: add missing extensions to .gitignore
>
>
>
> Mark Thompson (already merged)
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14537
>
> X [1/3] ffmpeg: Don't print graphs if there are no graphs to print
> X [2/3] fftools/graphprint: Fix leak of graphprint object
> X [3/3] fftools/graphprint: Fix leak of graph section header string
>
>
> softworkz
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14563
>
> X [1/5] fftools/makefile: Remove resources from ffprobe
> X [2/5] fftools/resources: Use .SECONDARY in Makefile comment
> X [3/5] fftools/ffmpeg: Free print_graph option variables
> X [4/5] fftools/graphprint: Fix memory leaks
> X [5/5] fftools/tf_mermaid: Add missing uninit and fix leaks
>
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14570
> X [v3] ffbuild/commonmak: Fix rebuild check with implicit rule chains
>
>
> Derek Buitenhuis
> https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14569
> (1/3 and 2/3 correspond to 2/3 from Timo, and 3/3 doesn't fix
> the rebuild check like "commonmak" above does)
>
> [1/3] ffbuild/common: Remove what appears to be a temporary debugging
> comment
> [2/3] ffbuild/common: Properly tag/suppress sed command
> [3/3] fftools/resoirces: Mark .css.min and .css.min.gz as NOTINTERMEDIATE
>
>
> Thanks again,
> sw
>

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.

Kieran

>
_______________________________________________
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:[~2025-05-21 11:00 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 [this message]
2025-05-21 20:05   ` softworkz .
2025-05-21 20:11   ` Kyle Swanson
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='CABGuwEkXQCKSKV9OPxCG0CoCHT2ALNpY+QBY=windK1_ZNtgvg@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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