Lynne<mailto:d...@lynne.ee>: >Sent: 2022年3月10日 18:42 >To: FFmpeg development discussions and patches<mailto:ffmpeg-devel@ffmpeg.org> >Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_blend_vulkan: add addition >blend mode > >9 Mar 2022, 19:19 by toq...@outlook.com: > >> Lynne<mailto:d...@lynne.ee>: >> >Sent: 2022年3月10日 1:43 >> >To: FFmpeg development discussions and >> >patches<mailto:ffmpeg-devel@ffmpeg.org> >> >Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_blend_vulkan: add addition >> >blend mode >> >>> >>> >>>> Ping. >>>> >> >>>From: Wu, Jianhua<mailto:jianhua.wu-at-intel....@ffmpeg.org> >> >>>> >Sent: 2022年2月25日 21:11 >>>> >>>>>To: ffmpeg-devel@ffmpeg.org<mailto:ffmpeg-devel@ffmpeg.org> >>>>>Subject: [FFmpeg-devel] [PATCH] avfilter/vf_blend_vulkan: add addition >>>>>blend mode >> >>>> >>>> >>> > >>> >> >None of them apply. Could you rebase them onto current git master >> I didn't see any new commits to vf_ blend_vulkan.c. Is there any conflict? >> > >Patches lack SHA1 ancesor, so they can't be applied. You must've made >them from a WIP repo. > > >>> and squash them into 1 commit? >>> >> Nope. This didn't break the contribution rules. My intention is to keep the >> commit message as clear as I can, which can help you test each mode quickly >> for they are completed not the same things, or other people who want to use >> the mode specified easily. >> > >It's just a few very obvious lines per patch, anyone can plainly >see how new modes are added. I can squash them when I push, >but if you did it, it would save me from having to download 10 >patches manually. >
Hi Lynne, Could you help do that? I sent the patches as attachments. It should be easy to download. The procedure of patches resending is too complicated and verbose for me. Thanks, Jianhua _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
