From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests Date: Thu, 13 Feb 2025 12:27:14 +0000 Message-ID: <BN0P223MB0358E801FE51516350F7D3F4BAFF2@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <BN0P223MB03582A299D224CCE08DD81D7BAFF2@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft > Works > Sent: Donnerstag, 13. Februar 2025 13:08 > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests > Oh, just while writing this reminded me that for the ffstaging (GitHub-sync-to- > ML) setup I had applied and been granted 10 parallel build jobs without > (monthly total) limit on Azure DevOps. Each job can run for 6h max, but you > can start a new one then. This means 10 build machines can run in parallel > 24/7 all time. > Since the application was "for building ffmpeg PRs" it would be perfectly fine > to use this capacity for our CI builds. > That way, we also do not need to be that much concerned about potential > abuse. This is set up as a separate "DevOps organization", which means that I'd be able to transfer ownership to ffmpeg. sw _______________________________________________ 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-02-13 12:27 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-12 18:06 Michael Niedermayer 2025-02-12 18:49 ` Lynne 2025-02-12 18:53 ` Romain Beauxis 2025-02-12 19:23 ` Lynne 2025-02-12 21:22 ` Stephen Hutchinson 2025-02-12 21:32 ` Timo Rothenpieler 2025-02-12 21:37 ` Soft Works 2025-02-12 21:51 ` Timo Rothenpieler 2025-02-12 22:01 ` Soft Works 2025-02-12 22:05 ` Timo Rothenpieler 2025-02-12 22:16 ` Soft Works 2025-02-12 23:29 ` Timo Rothenpieler 2025-02-12 23:34 ` Kieran Kunhya via ffmpeg-devel 2025-02-13 0:27 ` Timo Rothenpieler 2025-02-13 12:07 ` Tomas Härdin 2025-02-13 4:05 ` martin schitter 2025-02-13 8:49 ` Leo Izen 2025-02-13 9:27 ` Tanay Manerikar 2025-02-13 12:40 ` Leo Izen 2025-02-13 9:49 ` Gyan Doshi 2025-02-13 10:30 ` Soft Works 2025-02-13 12:37 ` Leo Izen 2025-02-13 13:32 ` Timo Rothenpieler 2025-02-12 22:12 ` Romain Beauxis 2025-02-12 23:22 ` Soft Works 2025-02-12 23:07 ` Soft Works 2025-02-12 23:34 ` Timo Rothenpieler 2025-02-13 0:17 ` Soft Works 2025-02-13 0:24 ` Romain Beauxis 2025-02-13 0:40 ` Soft Works 2025-02-13 1:52 ` Timo Rothenpieler 2025-02-13 2:59 ` Soft Works 2025-02-13 6:14 ` Lynne 2025-02-13 6:50 ` martin schitter 2025-02-13 6:54 ` Soft Works 2025-02-13 7:24 ` Soft Works 2025-02-13 13:32 ` Timo Rothenpieler 2025-02-13 11:04 ` Tobias Rapp 2025-02-13 12:07 ` Soft Works 2025-02-13 12:27 ` Soft Works [this message] 2025-02-13 13:37 ` Timo Rothenpieler 2025-02-13 12:10 ` Tomas Härdin 2025-02-13 12:38 ` martin schitter 2025-02-12 20:38 ` Michael Niedermayer
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=BN0P223MB0358E801FE51516350F7D3F4BAFF2@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@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