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: Re: [FFmpeg-devel] Graphprint Patches Reminder #2
Date: Tue, 27 May 2025 02:02:51 +0000
Message-ID: <DM8P223MB03658FCB172108BA9B7411E0BA64A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CALweWgA=9LZGK4CmLoc3AX17Wxu5D4Bg6B+Xwq1wVDjqdH4NaQ@mail.gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Ramiro Polla
> Sent: Dienstag, 27. Mai 2025 03:48
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Graphprint Patches Reminder #2
> 
> Hi,
> 
> On Mon, May 26, 2025 at 9:19 AM softworkz .
> <softworkz-at-hotmail.com@ffmpeg.org> wrote:
> > 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
> > [1/5] fftools/makefile: Remove resources from ffprobe
> > [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
> 
> The patches above should be ok to apply.
> 
> I just sent a new patchset to fix things a bit differently from the
> patches below. 

Do you know how time I've spent to get the intermediate handling right?
Means to work as per the actual way of Gnu make intermediate handling 
instead of working around by keeping the files alive somehow.

I had agreed with Timo that .ptx files are kept and all other intermediates
get deleted as by design. The v4 version of my patch does that.

Thanks,
sw
_______________________________________________
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-27  2:03 UTC|newest]

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