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] The "bad" Patch
Date: Fri, 30 May 2025 03:42:48 +0000
Message-ID: <DM8P223MB03652CC5F60F611DEFE4AA15BA61A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <aDhyqS__ip-LuPB_@phare.normalesup.org>

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Nicolas George
> Sent: Donnerstag, 29. Mai 2025 16:44
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The "bad" Patch
> 
> softworkz . (HE12025-05-28):
> >						 Also, I cannot
> > consider people as trustworthy while they are going crazy.
> 
> Oh, yes, I dare say insulting your betters is the best strategy.

I'm afraid to see you struggling with language issues. To explain it in 
simple words: We all can have moments where we might get 
crazy about something. That's why it would be unfair and insulting 
to say that people who are getting crazy are not trustworthy.

What has been said instead, is that people who've gone crazy are not 
trustworthy IN THAT MOMENT (=> "while").


> > Misunderstanding 1: What is being launched?
> > ===========================================
> 
> People have pointed to you the use of system() because it is an focal
> point of all the wrong things

Oh - when you have knowledge about "all the wrong things", then I'm sure
it won't take you - the knowledgeable senior mentor member - much
effort, to educate me - the unexperienced novice developer, who had - in his 
ignorance and lack of knowledge - accidentally chosen to use a "bad" API.
Please be specific by explaining what is wrong about the specific use case and language,
and which bad things could happen!?


> an easy way [is] to get into the
> documentation and learn about the issues of what you are doing.

This gives just testimony that you've never read that documentation.


> > I have no intentions towards getting this merged.
> 
> Good. Maybe get over yourself and find a safe way of implementing it

Nay. Which part is not understandable in my reply?


> instead of using it as an excuse to play the victim.

That's in fact a great new thing that I've learned just recently here:

What an incredibly ingenious attack it is to attack someone by
saying they should not play "the victim".


[2nd email]
> > That nobody has responded is not much surprising
> Yes, nobody responded after less than twelve hours, that must be a
> conspiracy.

Not at all - but if none have responded after 12h, how likely
would it remain to be for the 

have been to get responses from everybody?
I.e., the probability for all replying under the condition that
nobody would have replied within the first 12h.

Wasn't "Math" a kind of hobby of yours? (evening school?)
Maybe you can ask your teacher about how this works.


> Also, for pity's sake, stop sucking all the air from this mailing-list.

Oh well, this is just the prologue. The main chapter is yet to come.
But I'll give it a little time for the questions. These are serious and 
not of rhetorical nature.


Regards,
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-30  3:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 15:24 softworkz .
2025-05-28 17:34 ` Rémi Denis-Courmont
2025-05-28 18:01   ` softworkz .
2025-05-28 18:09     ` softworkz .
2025-05-28 18:27 ` Marton Balint
2025-05-28 18:46   ` softworkz .
2025-05-29  2:59 ` softworkz .
2025-05-29  9:55   ` Nicolas George
2025-05-31 11:44   ` softworkz .
2025-05-31 16:21     ` Mark Thompson
2025-05-31 18:28       ` softworkz .
2025-05-31 20:26         ` Mark Thompson
2025-06-02  6:09           ` softworkz .
2025-06-02  7:31           ` softworkz .
2025-05-31 16:59     ` softworkz .
2025-05-31 17:34       ` softworkz .
2025-06-01 23:21         ` Michael Niedermayer
2025-06-01 23:51           ` softworkz .
2025-06-02  7:57           ` Nicolas George
2025-06-02  9:31             ` softworkz .
2025-06-02 10:18               ` softworkz .
2025-06-02 10:49                 ` Nicolas George
2025-06-02 19:30                   ` softworkz .
2025-06-02 21:26                   ` softworkz .
2025-06-02 19:34             ` Michael Niedermayer
2025-06-02 21:22               ` softworkz .
2025-06-03  1:06                 ` Michael Niedermayer
2025-06-01 23:56         ` softworkz .
2025-05-31 18:38       ` Kieran Kunhya via ffmpeg-devel
2025-05-29 14:43 ` Nicolas George
2025-05-30  3:42   ` softworkz . [this message]
2025-05-31 19:31 ` Leo Izen
2025-05-31 19:34   ` Marvin Scholz
2025-05-31 20:08   ` softworkz .
2025-05-31 20:13     ` 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=DM8P223MB03652CC5F60F611DEFE4AA15BA61A@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