From: "Christopher Snowhill" <kode54@gmail.com> To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>, "Dmitriy Kovalenko" <dmtr.kovalenko@outlook.com> Cc: ffmpeg-devel <ffmpeg-devel-bounces@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 03:43:09 -0700 Message-ID: <DAAA87VB1H5S.1SPY1OTQR58EI@gmail.com> (raw) In-Reply-To: <b623cd7a-47af-c77c-8662-c4b941f14261@martin.st> On Sat May 31, 2025 at 3:03 AM PDT, Martin Storsjö wrote: > On Sat, 31 May 2025, Dmitriy Kovalenko wrote: > >> Great. I send another version with the reverted change for the asr >> register change. What is the correct process to reply for the inline >> changes then? Inline email answer or cover letter? > > Do not top post. Reply to review comments in an inline reply to the email > with the review. I hope they are not using the Outlook.com web interface to do their replying to this list. Most of the web mail silos do their worst to encourage top posting, or even make it impossible to do otherwise, by not allowing one to insert text into the middle of the quoted message. Unfortunately, it seems that handling email properly for mailing list based development often requires setting up proper clients. I've done the worst by dedicating an entire Linux container to running aerc and notmuch. However, there are definitely easier ways of handling development mail. Heck, I'm still using Gmail for this list, with an outside client, and I don't even know if my replies are reaching the list. Certainly, Gmail may be dropping my incoming list bound copies of my messages because of the headers. > > // Martin > > _______________________________________________ > 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".
next prev parent reply other threads:[~2025-05-31 10:43 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 [this message] 2025-05-31 10:49 ` Dmitriy Kovalenko
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=DAAA87VB1H5S.1SPY1OTQR58EI@gmail.com \ --to=kode54@gmail.com \ --cc=dmtr.kovalenko@outlook.com \ --cc=ffmpeg-devel-bounces@ffmpeg.org \ --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