From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
Date: Thu, 22 May 2025 14:57:34 +0000
Message-ID: <DM8P223MB03655935E37AB87ECFBD5235BA99A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB0365A221B0BF961AAE9DDE84BA99A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Donnerstag, 22. Mai 2025 16:14
> To: Kieran Kunhya <kieran618@googlemail.com>
> Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
>
>
>
> > > From: Kieran Kunhya <kieran618@googlemail.com>
> > > Sent: Donnerstag, 22. Mai 2025 16:07
> > > To: softworkz . <softworkz@hotmail.com>
> > > Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > > Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
> > >
> > >
> > > On Thu, 22 May 2025, 15:03 softworkz ., <mailto:softworkz@hotmail.com>
> wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: ffmpeg-devel <mailto:ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Kieran
> > > > Kunhya via ffmpeg-devel
> > > > Sent: Donnerstag, 22. Mai 2025 14:46
> > > > To: FFmpeg development discussions and patches <mailto:ffmpeg-
> devel@ffmpeg.org>
> > > > Cc: Kieran Kunhya <mailto:kieran618@googlemail.com>
> > > > Subject: Re: [FFmpeg-devel] Graphprint Patches Overview
> > > >
> > > > > I really wonder how Kieran can't be embarrassed trying such maneuvers
> which
> > > > > are so obvious to everybody.
> > > >
> > > > I really wonder how you can't be embarrassed sending what imo is the
> > > > worst patchset in the history of the project.
> > > > Instead of acknowledging that, it's deflecting and playing the victim
> > > > you want to do.
> > > >
> > > > Kieran
> > > > _______________________________________________
> > >
> > > I like that! Keep going. Was that all you got?
> > >
> > > sw
> >
> > A patchset so bad, people who quit the project like Derek came back to clean
> up your mess.
> >
> > Kieran
> >
> > people who quit the project like Derek came back
>
> That'd be too much of an honour - but really, it doesn't work like that.
> You need to keep focusing on saying bad and defaming things.
>
> Try again, I'm sure you can do better...
>
> sw
> _______________________________________________
What's up, running out of ideas?
Maybe get even more dirty - that's always a good idea when your points
have no substance, it emphasizes your dedication and makes it more credible
for everybody.
How about this:
Softworkz also ruined Christmas this year because he stole Santa's reindeer!
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-22 14:57 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 .
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 . [this message]
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=DM8P223MB03655935E37AB87ECFBD5235BA99A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=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