Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2023
Date: Sun, 15 Jan 2023 08:26:34 -0500
Message-ID: <CAEEMt2msJPZPMLD7a5JhKBZm=Xuorj+8CtmrTqj3+EX258UhVg@mail.gmail.com> (raw)
In-Reply-To: <CAFXK13efjheR6eLq5oCckbMc9fuWJ145jV7C5qnvZ+VoPnwOJA@mail.gmail.com>

Hi,

On Sun, Jan 15, 2023 at 4:20 AM Nuo Mi <nuomi2021@gmail.com> wrote:

> Is it finalized?  Any chance to add some items in
> https://github.com/ffvvc/FFmpeg/issues to the GSOC 2023?
>

It all depends on the student. And baseline ffvvc needs to be in already
when the project starts. So it's not straightforward.

Are you proposing to be the student? Or what's your plan?

Ronald
_______________________________________________
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".

  reply	other threads:[~2023-01-15 13:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 14:42 Thilo Borgmann
2022-12-15 14:47 ` Jean-Baptiste Kempf
2022-12-15 22:47   ` Pierre-Anthony Lemieux
2022-12-18 16:47     ` Thilo Borgmann
2023-01-15  9:20       ` Nuo Mi
2023-01-15 13:26         ` Ronald S. Bultje [this message]
2023-01-15 13:56           ` Jean-Baptiste Kempf
2023-01-15 14:31             ` Nuo Mi
2023-01-15 14:28           ` Nuo Mi
2023-01-15 22:18             ` Thilo Borgmann
2023-01-16 13:53               ` Nuo Mi
2023-01-16 14:58                 ` Jean-Baptiste Kempf
2023-01-17 15:22                   ` Nuo Mi
2023-01-19 11:10                     ` Nuo Mi
2023-01-23 10:50                       ` Thilo Borgmann
2023-01-24 13:16                         ` Nuo Mi
2023-02-23 19:27 ` Thilo Borgmann

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='CAEEMt2msJPZPMLD7a5JhKBZm=Xuorj+8CtmrTqj3+EX258UhVg@mail.gmail.com' \
    --to=rsbultje@gmail.com \
    --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