From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Forgejo questions Date: Fri, 25 Jul 2025 15:57:25 +0200 Message-ID: <20250725135725.GQ29660@pb2> (raw) In-Reply-To: <fb590697-61b8-45a0-b74c-4d5ec9950af1@rothenpieler.org> [-- Attachment #1.1: Type: text/plain, Size: 3112 bytes --] Hi On Thu, Jul 24, 2025 at 07:46:25PM +0200, Timo Rothenpieler wrote: > On 7/24/2025 7:30 PM, Michael Niedermayer wrote: > > Hi all > > > > how can i simply follow all changes, patches and discussions ? > > > > prior to teh forgejo test, i simply go over all new mail in my ffmpeg-devel > > folder. > > In that folder, > > I can leave things as new that i want to look at later > > I can mark things as old that i have not read but dont plan to do anything with > > I can mark things as read that i have looked at and am done with (like after applying them locally) > > I can press a single button to apply the patch from a mail > > I have just made a sieve filter that puts all mails from Forgejo into their > own folder, and I do have proper threads with all discussions (and pushes) > in there. Theres no threading as in: (PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) what i expected is: (PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) Re:(PR #123) So that one can see on first glance that there are 2 comments to the PR and then following discussion on top of these 2 comments > > 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 > > > I see https://code.ffmpeg.org/FFmpeg/FFmpeg/activity > > but that also seems not to really contain the level of detail that a simple > > threaded mailinglist with new mails shows > > > > Basically, can someone explain me how to use this effectively ? > > You should be able to use it exactly like you described, as long as you > don't expect actual patches to be in the mails. > Everything else, comments, discussion, ... should be in an E-Mail to you. ive subscribed now with a 2nd account for watching only so i can filter the watch all stuff away from things that i actively touched otherwise watching the repo results in my inbox duplicating everything from fffjo from ffmpeg-devel Maybe we should collect all these suggestions on how to effectively use forgejo in some place/file/wiki ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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 13:57 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 [this message] 2025-07-25 14:19 ` Kieran Kunhya via ffmpeg-devel 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=20250725135725.GQ29660@pb2 \ --to=michael@niedermayer.cc \ --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