Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_blend_vulkan: add addition blend mode
Date: Thu, 10 Mar 2022 13:03:25 +0100
Message-ID: <CAPYw7P62bfM79Yq=WVJqi3d38fbv2RHT83qs07KbpO=Yf-pa7Q@mail.gmail.com> (raw)
In-Reply-To: <OSZP286MB217335CC2F6ACB068320FD1DCA0B9@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM>

On Thu, Mar 10, 2022 at 12:58 PM Wu Jianhua <toqsxw@outlook.com> wrote:

> Lynne<mailto:dev@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 toqsxw@outlook.com:
> >
> >> Lynne<mailto:dev@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.com@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.
>

There is nothing to fix patches that does not apply.

Just send new patches for current master.


>
> 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-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
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:[~2022-03-10 12:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH0PR11MB49684654487C413853417112933E9@PH0PR11MB4968.namprd11.prod.outlook.com>
2022-02-25 13:10 ` Wu, Jianhua
2022-03-09 11:57   ` Wu Jianhua
2022-03-09 17:43     ` Lynne
2022-03-09 18:19       ` Wu Jianhua
2022-03-10 10:42         ` Lynne
2022-03-10 11:58           ` Wu Jianhua
2022-03-10 12:03             ` Paul B Mahol [this message]
2022-03-10 12:37               ` Wu Jianhua

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='CAPYw7P62bfM79Yq=WVJqi3d38fbv2RHT83qs07KbpO=Yf-pa7Q@mail.gmail.com' \
    --to=onemda@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