From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/4] doc/developer.texi: extend the argument for submitting patches Date: Mon, 14 Nov 2022 15:34:59 +0100 Message-ID: <166843649962.26119.12307610011247756962@lain.khirnov.net> (raw) In-Reply-To: =?utf-8?q?=3CDM8P223MB036513422AFA2EA338787F5BBA059=40DM8P223MB?= =?utf-8?q?0365=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?= Quoting Soft Works (2022-11-14 12:20:00) > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Anton Khirnov > > Sent: Monday, November 14, 2022 12:08 PM > > To: FFmpeg development discussions and patches <ffmpeg- > > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] [PATCH 2/4] doc/developer.texi: extend > > the argument for submitting patches > > > > Quoting Soft Works (2022-11-14 11:46:49) > > > > Sorry, but you problems are entirely self-inflicted. You have > > been > > > > told what changes need to happen right from the beginning, > > > > repeatedly, and by several developers independently. > > > > > > And those are completed and settled, like I had state multiple > > times. > > > It's ready for review for months already. > > > > Your stating something does not make it true, no matter how many > > times > > you do it. > > > > My objections were not addressed. > > > > In your last resend, Hendrik yet again raised the start_pts question. > > As > > far as I can tell, your explanation for why it's supposedly needed > > did > > not convince ANYONE. > > What means "as far as I can tell" here? Do you have something to > say about it, then please do? It means that I am not aware of anyone who changed their stance based on your arguments, but cannot prove that no such person exists. > > I cannot talk and respond to any "ghost" statements which I'm not > aware of. > > And regarding the IRC snippet: Well, interesting, but I can neither > know not respond to anything I'm not aware of. > > > I had taken the effort to explain the reasons this in this article: > > https://github.com/softworkz/SubtitleFilteringDemos/issues/1 > > and Hendrik didn't respond. So whom should I talk to, in order > to find a solution, especially, considering the fact, that > nobody has really taken the effort to ACTUALLY understand what > the problem is? I did read your document, and my takeaway message from it is "doing it properly is too hard". As long as that continues to be your position, you might as well not bother. -- Anton Khirnov _______________________________________________ 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:[~2022-11-14 14:35 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-14 9:13 [FFmpeg-devel] [PATCH 1/4] doc/developer.texi: improve the introductory text Anton Khirnov 2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 2/4] doc/developer.texi: extend the argument for submitting patches Anton Khirnov 2022-11-14 9:35 ` Soft Works 2022-11-14 9:53 ` Anton Khirnov 2022-11-14 10:46 ` Soft Works 2022-11-14 11:07 ` Anton Khirnov 2022-11-14 11:20 ` Soft Works 2022-11-14 11:40 ` Soft Works 2022-11-14 12:42 ` Nicolas George 2022-11-14 14:34 ` Anton Khirnov [this message] 2022-11-14 15:13 ` Soft Works 2022-11-14 15:18 ` Paul B Mahol 2022-11-14 15:39 ` Soft Works 2022-11-14 15:45 ` Soft Works 2022-11-14 16:13 ` Anton Khirnov 2022-11-14 16:38 ` Soft Works 2022-11-14 16:40 ` Nicolas George 2022-11-14 17:25 ` Soft Works 2022-11-14 17:47 ` Nicolas George 2022-11-14 22:05 ` Michael Niedermayer 2022-11-14 22:49 ` Soft Works 2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 3/4] doc/developer.texi: demote the "contributing" chapter to a section Anton Khirnov 2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 4/4] doc/developer.texi: refine the "contributing code" section Anton Khirnov
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=166843649962.26119.12307610011247756962@lain.khirnov.net \ --to=anton@khirnov.net \ --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