Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [TC] checkasm: use pointers for start/stop functions
Date: Tue, 25 Jul 2023 00:19:18 +0200 (CEST)
Message-ID: <Na8z3HG--3-9@lynne.ee> (raw)
In-Reply-To: <13eaceb-33c1-e82f-be73-e469836debde@martin.st>

Jul 24, 2023, 23:27 by martin@martin.st:

> On Mon, 17 Jul 2023, Rémi Denis-Courmont wrote:
>
>> Since you're giving zero valid reasons, I'm invoking the TC.
>>
>
> Just for public record and visibility:
>
> The TC has discussed the matter at hand. Overall, the TC considered that the approach of using an indirect call seemed tolerable given the benefits and could be accepted if necessary. But avoiding the indirect call unless there actually are multiple timing providers would be even better, retaining the same low overhead as before.
>
> As the updated patchset seems to implement that, we consider the case closed - and actual TC involvement wasn't needed after all here.
>
> // Martin Storsjö, on behalf of the FFmpeg Technical Committee
>

I do think TC involvement here was unnecessary - I do not object to this
version of the patch, so LGTM.
I do agree with the decision overall, but this is nothing that couldn't
be solved with a 3 minute discussion.

I think, however, the process has become rather opaque in this case.
Usually, there has to be a clear writeup of the issue, with all context
removed, that all parties have to agree on is presentable to the TC
for guidelines. In the past, whenever developers have thrown in random
comments for a TC discussion, this has been followed, and the TC
has not responded, but what makes this case so special, when this
was also the case?

Plus, even now, I have zero idea who is on the TC - it has been three years
since it was made, and although it's not meant to last for so long, I doubt
there's a need for a vote as the final results would probably remain the
same. But I would like to know who is still actively involved, and whether
all of the people on the TC discussed this, as it's necessary to make a decision.

If this was an informative guideline, rather than an actual decision where
all members voted and agreed, I think this should be stated.

If the TC were to actively get involved and give decisions without following
proper procedures, it would do more than what the TC was meant to do -
resolve issues.
_______________________________________________
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:[~2023-07-24 22:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 18:26 [FFmpeg-devel] [PATCH 0/7] checkasm RISC-V Linux perf enablement Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 1/7] checkasm: fix Linux perf cleanup Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 2/7] checkasm: improve Linux perf error message Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 3/7] checkasm: make perf macros functional Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 4/7] checkasm: use pointers for start/stop functions Rémi Denis-Courmont
2023-07-15  8:05   ` Lynne
2023-07-15  8:25     ` Rémi Denis-Courmont
2023-07-15 17:43       ` Lynne
2023-07-15 20:13         ` Rémi Denis-Courmont
2023-07-16 20:32           ` Lynne
2023-07-17  5:18             ` Rémi Denis-Courmont
2023-07-17 17:48               ` Lynne
2023-07-17 18:09                 ` Rémi Denis-Courmont
2023-07-18 21:32                   ` Lynne
2023-07-19 15:58                     ` Rémi Denis-Courmont
2023-07-24 21:26                   ` [FFmpeg-devel] [TC] " Martin Storsjö
2023-07-24 21:33                     ` Nicolas George
2023-07-24 22:19                     ` Lynne [this message]
2023-07-24 22:57                       ` Kieran Kunhya
2023-07-25  6:44                       ` Martin Storsjö
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 5/7] checkasm: remove unused variable Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 6/7] checkasm: allow run-time fallback to AV_READ_TIME Rémi Denis-Courmont
2023-07-14 18:28 ` [FFmpeg-devel] [PATCH 7/7] configure: enable Linux perf on RISC-V by default 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=Na8z3HG--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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