From: Kacper Michajlow <kasper93@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML?
Date: Sat, 2 Aug 2025 14:48:18 +0200
Message-ID: <CABPLASRQvkbcyU5hK2h7arWWpZB2=ZS3qD6+CKU5TYLmBZNsbg@mail.gmail.com> (raw)
In-Reply-To: <aI3hbKZTJAPFl_F8@phare.normalesup.org>
On Sat, 2 Aug 2025 at 11:59, Nicolas George <george@nsup.org> wrote:
>
> Romain Beauxis (HE12025-08-01):
> > Part of my question is: how should people know what are the area you
> > are responsible for and who to contact when working on specific areas?
>
> I know it and I am perfectly fine with reading the summary line of every
> submitted patch to see if I need to open it. Anything less would be
> irresponsible for somebody who have contributed to multiple parts of the
> code anyway.
>
> The issue is afterwards. Right now, if the summary tells me I should be
> interested, it takes me one key to start reading the patch and one key
> to start reviewing it. With the new proposal, it takes multiple clicks:
> that is not acceptable.
It's trivial to automatically download/preview patches, similar to how
attachments can be previewed if a patcheset is sent as an attachment.
- Kacper
_______________________________________________
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-08-02 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:42 Romain Beauxis
2025-07-29 21:52 ` Nicolas George
2025-08-01 23:17 ` Romain Beauxis
2025-08-02 9:59 ` Nicolas George
2025-08-02 12:48 ` Kacper Michajlow [this message]
2025-08-02 12:50 ` Nicolas George
2025-08-02 15:07 ` Romain Beauxis
2025-07-31 11:12 ` Rémi Denis-Courmont
2025-08-01 23:19 ` Romain Beauxis
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='CABPLASRQvkbcyU5hK2h7arWWpZB2=ZS3qD6+CKU5TYLmBZNsbg@mail.gmail.com' \
--to=kasper93@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