From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 0/6] ICC profile support in avcodec
Date: Tue, 26 Jul 2022 12:24:20 +0200
Message-ID: <20220726122420.GB19131@haasn.xyz> (raw)
In-Reply-To: <20220723123105.GB23484@haasn.xyz>
On Sat, 23 Jul 2022 12:31:05 +0200 Niklas Haas <ffmpeg@haasn.xyz> wrote:
> On Tue, 19 Jul 2022 14:26:02 +0200 Niklas Haas <ffmpeg@haasn.xyz> wrote:
> > Changes in v3:
> > - switch from `int icc_profiles` to a new AV_CODEC_FLAG2 to avoid ABI
> > break
> > - rebased onto master and fixed merge conflicts
> >
> > Changes in v2:
> > - remove unnecessary import
> > - fixed assignment-instead-of-equality
> > - fixed #ifdef -> #if
>
> Ping. Any objections to merging as-is?
Will apply in 48h if there are no further comments.
_______________________________________________
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".
prev parent reply other threads:[~2022-07-26 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 12:26 Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 1/6] fflcms2: move to libavcodec Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 2/6] avcodec/codec_internal: add cap for ICC profile support Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 3/6] avcodec: add API for automatic handling of icc profiles Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 4/6] avcodec: add common fflcms2 boilerplate Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 5/6] avcodec/decode: parse ICC profiles Niklas Haas
2022-07-19 12:26 ` [FFmpeg-devel] [PATCH v3 6/6] avcodec/encode:: generate " Niklas Haas
2022-07-23 10:31 ` [FFmpeg-devel] [PATCH v3 0/6] ICC profile support in avcodec Niklas Haas
2022-07-26 10:24 ` Niklas Haas [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=20220726122420.GB19131@haasn.xyz \
--to=ffmpeg@haasn.xyz \
--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