From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Make tests a requirement
Date: Tue, 4 Jul 2023 13:32:25 +0200
Message-ID: <ZKQDSZHe+BVfaSC4@phare.normalesup.org> (raw)
In-Reply-To: <CAPYw7P6_7S0jO1P7z0o1h-RDnvFwU-UoRU-PGNgfBc2rGMNaEg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 799 bytes --]
Paul B Mahol (12023-07-04):
> Tyrants and dictators.
I would not have said it that way, but you are not wrong.
While in theory it would be nice to have tests for all new code, the
entitlement of the members of this project who contribute little code or
none at all who demand ever more and more from those who do is sincerely
disgusting.
They think they can get away with it because they believe they control
access to the project and the prestige of being published in FFmpeg will
push anybody to jump through hoops. Well, they are wrong on the second
point, nothing new happened in FFmpeg except interfacing with other
code, the prestige is melting like a glacier in the XXIst century. So
let us make sure they are wrong on the first point.
Regards,
--
Nicolas George
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 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:[~2023-07-04 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 23:00 Michael Niedermayer
2023-07-03 23:31 ` Tomas Härdin
2023-07-04 1:38 ` Paul B Mahol
2023-07-04 9:01 ` Tomas Härdin
2023-07-04 11:32 ` Nicolas George [this message]
2023-07-04 3:04 ` Pierre-Anthony Lemieux
2023-07-04 9:02 ` Jean-Baptiste Kempf
2023-07-04 14:56 ` Rémi Denis-Courmont
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=ZKQDSZHe+BVfaSC4@phare.normalesup.org \
--to=george@nsup.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