From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [TC] "Future Log Output Default" Date: Sat, 26 Apr 2025 17:10:27 +0200 Message-ID: <20250426151027.GF4991@pb2> (raw) [-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --] Hi all This is just an announcement that the TC has been asked to look into avutil/log: Add log flag to control printing of memory addresses GitHub: https://github.com/ffstaging/FFmpeg/pull/59 Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14094 ... and the disagreement between people about it. So far, Niklas, Martin and myself have commented, there have been no formal decissions and no votes, we just since yesterday send some comments. From these to me it seems the TC members who spoke so far seem to agree that the addresses in the log are "mostly noise". I wonder a bit if the TC discussions should/could be more public but thats a subject for a different thread. Myself summarizing will surely miss some fine points but iam trying anyway. Niklas also brought up that item_name() is used in filters to disambiguate instances and that we maybe could add a const char *name and have fftools genrate a unique ID for each Either way none of this is a TC decission or binding its just a partial summary of the things that TC members said thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you fake or manipulate statistics in a paper in physics you will never get a job again. If you fake or manipulate statistics in a paper in medicin you will get a job for life at the pharma industry. [-- 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".
next reply other threads:[~2025-04-26 15:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-26 15:10 Michael Niedermayer [this message] 2025-04-26 15:22 ` Michael Niedermayer 2025-04-26 16:28 ` softworkz . 2025-04-27 8:28 ` 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=20250426151027.GF4991@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