Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v6 01/14] vvcdec: add vvc decoder stub
Date: Thu, 7 Dec 2023 13:13:14 -0300
Message-ID: <7cca8974-9e87-45f5-84b1-fb80d8f4bf6c@gmail.com> (raw)
In-Reply-To: <170196527757.8914.798909765390964834@lain.khirnov.net>

On 12/7/2023 1:07 PM, Anton Khirnov wrote:
> Quoting James Almer (2023-12-06 23:50:19)
>> On 12/5/2023 11:45 AM, Nuo Mi wrote:
>>> ---
>>>    configure               |   1 +
>>>    libavcodec/Makefile     |   1 +
>>>    libavcodec/allcodecs.c  |   1 +
>>>    libavcodec/vvc/Makefile |   4 +
>>>    libavcodec/vvc/vvcdec.c |  62 ++++++++++++
>>>    libavcodec/vvc/vvcdec.h | 204 ++++++++++++++++++++++++++++++++++++++++
>>>    6 files changed, 273 insertions(+)
>>>    create mode 100644 libavcodec/vvc/Makefile
>>>    create mode 100644 libavcodec/vvc/vvcdec.c
>>>    create mode 100644 libavcodec/vvc/vvcdec.h
>>
>> I'll be squashing
> 
> why?

Why do you want a commit that adds a decoder with empty callbacks?

I wasn't going to squash the entire set into one commit, just this one 
with the last. But if you prefer it to go in like this, then i'll push 
as is.
_______________________________________________
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:[~2023-12-07 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 14:45 Nuo Mi
2023-12-06 22:50 ` James Almer
2023-12-07 16:07   ` Anton Khirnov
2023-12-07 16:13     ` James Almer [this message]
2023-12-07 16:35       ` Anton Khirnov
2023-12-08  1:01       ` Nuo Mi

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=7cca8974-9e87-45f5-84b1-fb80d8f4bf6c@gmail.com \
    --to=jamrial@gmail.com \
    --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