From: Wu Jianhua <toqsxw@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 5/5] avfilter/vf_blend: fix un-checked potential memory allocation failure
Date: Mon, 3 Jan 2022 14:48:27 +0000
Message-ID: <TYCPR01MB5984AF457EFE52CEAC583368CA499@TYCPR01MB5984.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <b880f19e-6771-cea8-33c0-07a01c5a549a@rothenpieler.org>
Timo Rothenpieler<mailto:timo@rothenpieler.org> wrote:
> On 03.01.2022 09:39, Wu, Jianhua wrote:
>> And there is one more question, may I know why there is a suffix "@ffmpeg.org"
>> behind my commit Author email?
>
> Your E-Mail server is enforcing strict policy via DKIM/DMARC, so it's
> impossible for any other mail-servers, like mailing lists, to send
> E-Mails from @intel.com.
> Hence the only option the list server has is to mangle the sender
> address like that.
Got it. Thanks for your answer. Maybe it's better to send patches as attachments in case the commit message gets broken.
Best Regards,
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".
prev parent reply other threads:[~2022-01-03 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 14:51 [FFmpeg-devel] [PATCH 1/5] avutil/hwcontext_vulkan: fixed validation error VUID 01387 Wu Jianhua
2022-01-02 14:51 ` [FFmpeg-devel] [PATCH 2/5] transpose_vulkan: add passthrough option Wu Jianhua
2022-01-10 14:19 ` Anton Khirnov
2022-01-10 15:52 ` Wu Jianhua
2022-01-02 14:51 ` [FFmpeg-devel] [PATCH 3/5] avfilter/vf_scale_vulkan: align struct ScaleVulkanContext Wu Jianhua
2022-01-02 14:51 ` [FFmpeg-devel] [PATCH 4/5] avfilter: add a blend_vulkan filter Wu Jianhua
2022-01-02 14:51 ` [FFmpeg-devel] [PATCH 5/5] avfilter/vf_blend: fix un-checked potential memory allocation failure Wu Jianhua
2022-01-03 2:23 ` Lynne
2022-01-03 8:39 ` Wu, Jianhua
2022-01-03 13:57 ` Timo Rothenpieler
2022-01-03 14:48 ` Wu Jianhua [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=TYCPR01MB5984AF457EFE52CEAC583368CA499@TYCPR01MB5984.jpnprd01.prod.outlook.com \
--to=toqsxw@outlook.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