From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Kieran Kunhya <kieran618@googlemail.com> Subject: Re: [FFmpeg-devel] Forgejo questions Date: Fri, 25 Jul 2025 15:19:03 +0100 Message-ID: <CABGuwEm=h8BNGY9iE+XrCTkKPRBMhcR3O62syU4=S9Ccw_hePQ@mail.gmail.com> (raw) In-Reply-To: <20250725135725.GQ29660@pb2> > > > > > Maybe some spam filter is somehow interfering, and eating some mails? > > > > > Going over the whole list is not particularly difficult (the contents > of > > > mails and patches may be difficult but the managing of mails/patches > is not) > > > > > > But with forgejo now there are mails in my inbox, in ffmpeg-devel > neither > > > seem to contain patches, nor do they seem to represent dicussions with > > > correct threading. I dont even know from 3 mails which is a reply to > which. > > > > The mails will never contain patches, they're just notifications. > > They do contain a link to the patches and the PR number to fetch it via > CLI > > though. > > why dont the mails contain the patches ? > is there a disadvantage ? > Especially with simple like 1 line patches being able to just see it > straight > could be nice > Because you're meant to review patches inline on the web app. Inline review, discussion and resolution on a web app is light years ahead of email. Kieran > _______________________________________________ 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-07-25 14:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-24 17:30 Michael Niedermayer 2025-07-24 17:46 ` Timo Rothenpieler 2025-07-24 17:58 ` Kyle Swanson 2025-07-24 18:03 ` Timo Rothenpieler 2025-07-25 13:57 ` Michael Niedermayer 2025-07-25 14:19 ` Kieran Kunhya via ffmpeg-devel [this message] 2025-07-25 14:30 ` Nicolas George
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='CABGuwEm=h8BNGY9iE+XrCTkKPRBMhcR3O62syU4=S9Ccw_hePQ@mail.gmail.com' \ --to=ffmpeg-devel@ffmpeg.org \ --cc=kieran618@googlemail.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