From: "Martin Storsjö" <martin@martin.st>
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 09:44:58 +0300 (EEST)
Message-ID: <8444ebba-8b38-1fc2-55a6-b7f4195ca13@martin.st> (raw)
In-Reply-To: <Na8z3HG--3-9@lynne.ee>
On Tue, 25 Jul 2023, Lynne wrote:
> 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?
This case was admittedly very opaque. I've seen numerous cases threatening
to escalate disputes to the TC. The difference here was that an actual
direct mail was sent to the TC requesting to take a stance on the matter
to unblock the patch. It wasn't a case of the TC deciding on its own to
get involved.
Now admittedly, to follow correct procedures, the TC should have announced
on the ML that we are discussing this issue and trying to make a decision.
Unfortunately I didn't notice that part in the description of procedures
until the discussion was done (and the patch review on the ML had
progressed with a new patchset that made good progress anyway), but we
wanted to make it publicly known that we had been invoked and actually had
had a discussion on the matter and made a decision, as was requested.
// Martin
_______________________________________________
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-25 6:45 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
2023-07-24 22:57 ` Kieran Kunhya
2023-07-25 6:44 ` Martin Storsjö [this message]
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=8444ebba-8b38-1fc2-55a6-b7f4195ca13@martin.st \
--to=martin@martin.st \
--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