From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] Forgejo questions Date: Thu, 24 Jul 2025 19:30:08 +0200 Message-ID: <20250724173008.GP29660@pb2> (raw) [-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --] 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 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. 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 ? I have figured out that with fetch = +refs/pull/*/head:refs/remotes/fforge/pr/* i can get all pull requests into my local git nicely thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are too smart to engage in politics are punished by being governed by those who are dumber. -- Plato [-- 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 reply other threads:[~2025-07-24 17:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-24 17:30 Michael Niedermayer [this message] 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 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=20250724173008.GP29660@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