From: Sean McGovern <gseanmcg@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] GSoC 2025
Date: Thu, 30 Jan 2025 05:21:39 -0500
Message-ID: <CAPBf_O=SWvMk6rsDjOMX23FknqjBwkkpRVKRUx+YojMjUOP=zA@mail.gmail.com> (raw)
In-Reply-To: <CABLWnS-qVRHjdw4vrh-mvgx_8RkYvx0sZGxeoah78RN-mWj9vg@mail.gmail.com>
Hi,
On Thu, Jan 30, 2025 at 1:36 AM Vittorio Giovara
<vittorio.giovara@gmail.com> wrote:
>
> On Wed, Jan 29, 2025 at 9:02 PM Ronald S. Bultje <rsbultje@gmail.com> wrote:
>
> > Hi,
> >
> > On Wed, Jan 29, 2025 at 2:32 PM Kieran Kunhya via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> > > It's clear the contribution method is outdated and difficult to
> > > manage. We need to move to GitLab ASAP
> >
> >
> > Yes please.
> >
> > Ronald
> >
>
> +1
> --
> Vittorio
> _______________________________________________
Also yes please -- I'm not particularly attached to GitLab
specifically even though I have my own instance of it running locally.
Any CI/CD tool would be better than this.
-- Sean McGovern
_______________________________________________
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-01-30 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 2:21 Michael Niedermayer
2025-01-29 15:51 ` Yigithan Yigit
2025-01-29 19:01 ` Michael Niedermayer
2025-01-29 19:31 ` Kieran Kunhya via ffmpeg-devel
2025-01-29 20:01 ` Ronald S. Bultje
2025-01-30 6:36 ` Vittorio Giovara
2025-01-30 10:21 ` Sean McGovern [this message]
2025-01-30 18:40 ` Michael Niedermayer
2025-01-30 21:20 ` Koushik Dutta
2025-01-30 14:53 ` compn
2025-01-31 5:01 ` Soft Works
2025-01-31 0:24 ` Vittorio Giovara
2025-01-31 12:51 ` James Almer
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='CAPBf_O=SWvMk6rsDjOMX23FknqjBwkkpRVKRUx+YojMjUOP=zA@mail.gmail.com' \
--to=gseanmcg@gmail.com \
--cc=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