Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12dec.c: rename 0x0502 CC format
Date: Sat, 25 Jan 2025 16:52:27 -0600
Message-ID: <CA+28BfCj2PM_ZCWebSOK-Rk5UfwsjgCHwrJ_xtr9e9S7dgygNQ@mail.gmail.com> (raw)
In-Reply-To: <8ea4389a-54d5-136e-5f34-0c1c1109b62e@passwd.hu>

Hello,

I am to blame here for suggesting DVB_0502 as the name.
I realize it was not the best choice and apologize for wasting your
cycles on this.

Looping in Keiran as we had discussed this over IRC briefly a few weeks back.
As I don't know how many networks actually use this in the wild, it
could be one or more,

How does something like this sound? CC_FORMAT_USERDATA_0502
_______________________________________________
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".

  reply	other threads:[~2025-01-25 22:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 20:26 Scott Theisen
2025-01-25 20:39 ` Marton Balint
2025-01-25 22:52   ` Marth64 [this message]
2025-01-25 23:28     ` Kieran Kunhya via ffmpeg-devel
2025-01-25 23:53       ` Scott Theisen
2025-01-26  0:07         ` Soft Works
2025-01-26  0:13           ` Marth64
2025-01-26  0:30             ` Soft Works
2025-01-26 10:04               ` Kieran Kunhya via ffmpeg-devel
2025-01-26 23:00                 ` Soft Works
2025-01-26 23:11                   ` Kieran Kunhya via ffmpeg-devel
2025-01-27  0:34                     ` Marth64
2025-02-02 18:55                       ` [FFmpeg-devel] [PATCH v2] " Scott Theisen
2025-02-03  2:40                         ` Marth64

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=CA+28BfCj2PM_ZCWebSOK-Rk5UfwsjgCHwrJ_xtr9e9S7dgygNQ@mail.gmail.com \
    --to=marth64@proxyid.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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