From: Dmitriy Kovalenko <dmtr.kovalenko@outlook.com>
To: Christopher Snowhill <kode54@gmail.com>
Cc: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 2/2] swscale: Neon rgb_to_yuv_half process 32 pixels at a time
Date: Sat, 31 May 2025 10:49:33 +0000
Message-ID: <DBAP193MB09562EC1170A4A8BE5D9BABA8D60A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DAAA87VB1H5S.1SPY1OTQR58EI@gmail.com>
I’m sorry for being slightly out of the process with my emails. I used the send-email and just thought it will be either to annotate the patches using cover letter but it seems like it is doing something weird with the messages.
> by
not allowing one to insert text into the middle of the quoted message.
You can still use “>” to make a partial quote (hope it works lol)
Best regards,
Dmitriy Kovalenko
> On May 31, 2025, at 12:43, Christopher Snowhill <kode54@gmail.com> wrote:
>
> by
> not allowing one to insert text into the middle of the quoted message.
_______________________________________________
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:[~2025-05-31 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250530084042.33204-1-dmtr.kovalenko@outlook.com>
2025-05-30 8:40 ` Dmitriy Kovalenko
2025-05-30 9:10 ` Martin Storsjö
2025-05-31 8:59 ` Dmitriy Kovalenko
2025-05-31 10:03 ` Martin Storsjö
2025-05-31 10:43 ` Christopher Snowhill
2025-05-31 10:49 ` Dmitriy Kovalenko [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=DBAP193MB09562EC1170A4A8BE5D9BABA8D60A@DBAP193MB0956.EURP193.PROD.OUTLOOK.COM \
--to=dmtr.kovalenko@outlook.com \
--cc=ffmpeg-devel-bounces@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=kode54@gmail.com \
/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