Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/4] avfilter/graphdump: implement options parsing
Date: Sun, 2 Mar 2025 00:22:43 +0100
Message-ID: <20250301232243.GZ4991@pb2> (raw)
In-Reply-To: <Z8HKcREQUEWKgtgV@phare.normalesup.org>


[-- Attachment #1.1: Type: text/plain, Size: 1364 bytes --]

Hi Nicolas

On Fri, Feb 28, 2025 at 03:38:41PM +0100, Nicolas George wrote:
> James Almer (HE12025-02-28):
> > Who among those still around after last Christmas (and in the TC, or
> > ultimately the GA, both of which would have a last word) is against your fun
> > things?
> 
> I could give you names, but you know them as well as me. The issue is
> that they have that authority in the first place, whether they make use
> of it or not.

I cannot find anything that says how the TC and maintainers relate in authority
Also i dont think the TC would override a clear decission of an active
maintainer even if it had the power to. The maintainer likely would resign
in such a case

About AVWriter.
I dont think this is a question for the TC
It is a question for the community because strings touch many parts
of FFmpeg and thus it affects many developers.

Strings in C are security wise, bad. Having some simple to use and safe
general API for string handling, IMHO makes sense.
reaching a point where everyone who may be affected by a string API
is ok with the code, is cerainly not easy, but i think we should not
give up.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are too smart to engage in politics are punished by being
governed by those who are dumber. -- Plato 

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".

      parent reply	other threads:[~2025-03-01 23:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 12:46 Niklas Haas
2025-02-18 12:46 ` [FFmpeg-devel] [PATCH v2 2/4] avfilter/filters: keep track of AVFilterPad labels Niklas Haas
2025-02-18 12:46 ` [FFmpeg-devel] [PATCH v2 3/4] avfilter/graphdump: add complex format Niklas Haas
2025-02-18 12:46 ` [FFmpeg-devel] [PATCH v2 4/4] fftools/ffmpeg_filter: add -dump_filter_graph option Niklas Haas
2025-02-18 16:43   ` epirat07
2025-02-19 17:36     ` Niklas Haas
2025-02-18 12:50 ` [FFmpeg-devel] [PATCH v2 1/4] avfilter/graphdump: implement options parsing Niklas Haas
2025-02-27 17:53 ` Niklas Haas
2025-02-27 21:17   ` Soft Works
2025-02-28  8:59   ` Nicolas George
2025-02-28 14:06     ` James Almer
2025-02-28 14:13       ` Nicolas George
2025-02-28 14:27         ` James Almer
2025-02-28 14:38           ` Nicolas George
2025-02-28 14:42             ` James Almer
2025-02-28 14:50               ` Nicolas George
2025-02-28 15:11                 ` James Almer
2025-02-28 15:16                   ` Nicolas George
2025-02-28 17:08                     ` Vittorio Giovara
2025-03-01 23:22             ` Michael Niedermayer [this message]

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=20250301232243.GZ4991@pb2 \
    --to=michael@niedermayer.cc \
    --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