From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
Date: Sat, 31 May 2025 21:38:28 +0000
Message-ID: <DM8P223MB0365FD35557C3D540B31B988BA60A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <aC7lRtdnyHouzCR8@phare.normalesup.org>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Nicolas
> George
> Sent: Donnerstag, 22. Mai 2025 10:50
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
>
> Kieran Kunhya via ffmpeg-devel (HE12025-05-22):
> > It's obvious basic testing was not done on this patchset seeing the scale
> > of memory leaks.
> >
> > I would like the TC to decide on reverting and proper resubmission later.
>
> For once, I agree with that assessment. I think giving softworkz the
> authority to decide if his own patches are ready for inclusion was
> premature.
>
> Regards,
>
> --
> Nicolas George
> _______________________________________________
For background and aftermath, please read: The "bad" Patch
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2025-May/344274.html
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".
next prev parent reply other threads:[~2025-05-31 21:38 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
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 . [this message]
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=DM8P223MB0365FD35557C3D540B31B988BA60A@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