Re: [FFmpeg-devel] [PATCH] lavfi: protection against premultiplied alpha (was: The patch series about premultiplied alpha)

[Kacper Michajlow <kasper93@gmail.com>]

On Sun, 3 Aug 2025 at 22:04, Michael Niedermayer <michael@niedermayer.cc> wrote:
>
> Hi
>
> On Sun, Aug 03, 2025 at 08:15:09PM +0200, Nicolas George wrote:
> > Nicolas George (HE12025-08-03):
> > > I will send the series here in a few hours.
> >
> > Here is a series of patch. I am absolutely not sure I found all the
> > filters that could be flagged, but the rest can be done as the need
> > arises.
> >
> > Not tested every filter, but it is pretty straightforward.
> >
>
> > I could not find how to download your patch series in a format suitable
> > for git am from the monster, I used the v2 series, but it should not
> > change anything.
>
> the easiest way to get the latest pull req from forgejo is to add
> the 3rd line of this to your git config matching your remote name for forgejo
>
> [remote "fforge"]
> url = git@code.ffmpeg.org:FFmpeg/FFmpeg.git
> fetch = +refs/heads/*:refs/remotes/fforge/*
> fetch = +refs/pull/*/head:refs/remotes/fforge/pr/*
>
> than a simple
> git fetch  fforge
>
> will simply fetch all the new pull requests;
>
> remote: Enumerating objects: 292, done.
> remote: Counting objects: 100% (202/202), done.
> remote: Compressing objects: 100% (140/140), done.
> remote: Total 140 (delta 106), reused 0 (delta 0), pack-reused 0 (from 0)
> Receiving objects: 100% (140/140), 26.96 KiB | 1.80 MiB/s, done.
> Resolving deltas: 100% (106/106), completed with 43 local objects.
> From code.ffmpeg.org:FFmpeg/FFmpeg
>    16d663d3713..d5f7a428b1e  master               -> fforge/master
>  + 4f5d8d6d83e...e700be74501 refs/pull/20023/head -> fforge/pr/20023  (forced update)
>  + 365709cea13...b48b607e18e refs/pull/20026/head -> fforge/pr/20026  (forced update)
>  + 7c25b6966e5...999e3e9bf80 refs/pull/20076/head -> fforge/pr/20076  (forced update)
>  + 79806960d83...5173c8db79f refs/pull/20080/head -> fforge/pr/20080  (forced update)
>  + f80bfa6791f...f63ea15605a refs/pull/20088/head -> fforge/pr/20088  (forced update)
>  + 0a38a1aeebf...901036493d5 refs/pull/20091/head -> fforge/pr/20091  (forced update)
>  + ca981fb1b03...6b07a40fd67 refs/pull/20092/head -> fforge/pr/20092  (forced update)
>  + 65ffc657982...95bd0614f6b refs/pull/20094/head -> fforge/pr/20094  (forced update)
>  * [new ref]                 refs/pull/20096/head -> fforge/pr/20096
>  * [new ref]                 refs/pull/20097/head -> fforge/pr/20097
>  * [new ref]                 refs/pull/20098/head -> fforge/pr/20098
>  * [new ref]                 refs/pull/20099/head -> fforge/pr/20099
>  * [new ref]                 refs/pull/20101/head -> fforge/pr/20101
>  * [new ref]                 refs/pull/20102/head -> fforge/pr/20102
>  * [new ref]                 refs/pull/20103/head -> fforge/pr/20103
>
>
> then simply a
> git merge fforge/pr/20031
>
> will merge the specified pull request
>

If you prefer to not have all PR fetched on each remote update, it's
possible to do on demand with

git fetch upstream pull/20031/head && git merge FETCH_HEAD

The end result is the same.

- Kacper
_______________________________________________
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".