From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] avfilter: fix data type for {Tile, Untile}Context's image size Date: Wed, 24 Jul 2024 00:10:08 +0200 Message-ID: <20240723221008.GG4991@pb2> (raw) In-Reply-To: <540a3283-5bfd-4452-986d-107190ba4405@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1851 bytes --] On Tue, Jul 23, 2024 at 12:17:43PM -0300, James Almer wrote: > On 7/19/2024 12:31 PM, Paul B Mahol wrote: > > Internal/private filter structures/API changes does not need be mentioned > > in that file, isn't that fact obvious even for average Joe? > > There's no reason to be condescending or aggressive over something so > irrelevant. Is it so hard to just state the APIChanges entry is not needed? "so irrelevant" sounds condescending to me too either way, i support pointing out if something sounds rude/condescending/aggressive (theres nothing bad in pointing that out, first step is always being aware one said something that others find offensive) > > I'm writing this representing the CC. This is not the only case you were > pointlessly aggressive to someone in the past week or so. Consider it a > warning before further action is taken. This part i do not agree with. First, i dont think we actually had a majority for a warning, I see 4 of 5 members of the CC replying but only 2 talking about a warning. Also (as i said previously) Politely pointing out to people when they write offensive things is a good thing, it has been effective in channeling discussions into a positive and friendlier direction, especially when done in real time. (You did the previously several times successfully) Adding a "threat" in the form of a warning maybe works for some people in some cases. But in others its more like slapping an already angry guy in the face. You get slapped harder back then have to punch and get punched back and then things spiral downward. And whetaver the exact outcome its a bad outcome thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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:[~2024-07-23 22:10 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-08 19:00 [FFmpeg-devel] [PATCH] Mention that AV_OPT_TYPE_IMAGE_SIZE can be unsigned Andrew Sayers 2024-07-08 19:40 ` Marcus B Spencer 2024-07-08 19:59 ` [FFmpeg-devel] [PATCH v2] lavu/opt: " Andrew Sayers 2024-07-10 14:01 ` Paul B Mahol 2024-07-10 14:54 ` Andrew Sayers 2024-07-19 12:54 ` James Almer 2024-07-19 13:54 ` [FFmpeg-devel] [PATCH v2] avfilter: fix data type for {Tile, Untile}Context's image size Andrew Sayers 2024-07-19 15:31 ` Paul B Mahol 2024-07-19 15:45 ` Andrew Sayers 2024-07-23 14:42 ` [FFmpeg-devel] [PATCH v4] " Andrew Sayers 2024-07-23 15:17 ` [FFmpeg-devel] [PATCH v2] " James Almer 2024-07-23 16:17 ` Paul B Mahol 2024-07-23 16:24 ` Paul B Mahol 2024-07-23 16:36 ` James Almer 2024-07-23 20:00 ` Ronald S. Bultje 2024-07-23 22:10 ` Michael Niedermayer [this message] 2024-07-24 4:32 ` Michael Niedermayer 2024-07-24 4:49 ` Marvin Scholz (ePirat) 2024-07-24 13:08 ` Michael Niedermayer 2024-07-24 19:33 ` Rémi Denis-Courmont 2024-07-25 7:54 ` Ronald S. Bultje 2024-07-25 10:12 ` Rémi Denis-Courmont 2024-07-19 8:34 ` [FFmpeg-devel] [PATCH v2] lavu/opt: Mention that AV_OPT_TYPE_IMAGE_SIZE can be unsigned Andrew Sayers 2024-07-19 12:42 ` Paul B Mahol
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=20240723221008.GG4991@pb2 \ --to=michael@niedermayer.cc \ --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