Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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 12:07:46 +0100
Message-ID: <166842406666.1198.894449822855148822@lain.khirnov.net> (raw)
In-Reply-To: =?utf-8?q?=3CDM8P223MB036561155B42D7767C8DD155BA059=40DM8P223MB?= =?utf-8?q?0365=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?=

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.

Some random quotes from IRC:
2022-09-01 00:25:21     @Lynne  elenril: I never retracted my insistence on using the native frame fields for subtitles
2022-09-01 00:25:27     @Lynne  not sure how softworks got that idea

2022-09-01 02:23:50     @BBB    subtitle.start_pts is really the emblem of the whole problem, I feel
2022-09-01 02:24:04     @BBB    there's many issues. but that one demonstrates it

-- 
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".

  parent reply	other threads:[~2022-11-14 11:07 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 [this message]
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
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=166842406666.1198.894449822855148822@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