Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Graphprint Patches Reminder #2
Date: Mon, 26 May 2025 07:19:34 +0000
Message-ID: <DM8P223MB0365BCE92251E92A94496535BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)

Hi,

if there are no objections, I would apply the patches below tomorrow evening.
Please let me know when you need more time or you have any concerns.

Note: The last one has been updated (v4) to always keep .ptx files (as requested
by Timo Rothenpieler).

Thanks
sw



[2/3] ffbuild: correctly silence and tag new css/html steps

[3/3] fftools/resources: add missing extensions to .gitignore

[1/5] fftools/makefile: Remove resources from ffprobe

[2/5] fftools/resources: Use .SECONDARY in Makefile comment

[3/5] fftools/ffmpeg: Free print_graph option variables

[4/5] fftools/graphprint: Fix memory leaks

[5/5] fftools/tf_mermaid: Add missing uninit and fix leaks

[v4]  ffbuild/commonmak: Fix rebuild check with implicit rule chains

Links

https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14528

https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14563

https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14570




_______________________________________________
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-26  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  7:19 softworkz . [this message]
2025-05-27  1:48 ` Ramiro Polla
2025-05-27  2:02   ` softworkz .
2025-05-27  2:56   ` softworkz .

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=DM8P223MB0365BCE92251E92A94496535BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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