From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] [RFC] GSoC 2025 SDR Cleanup
Date: Wed, 12 Feb 2025 02:17:47 +0000
Message-ID: <CABGuwE=kCnHMnWEyGJKxCV=nPC7=BPtjOM=+mdWhFHHbhyhg1g@mail.gmail.com> (raw)
In-Reply-To: <20250212021131.GM4991@pb2>
On Wed, 12 Feb 2025, 02:11 Michael Niedermayer, <michael@niedermayer.cc>
wrote:
> On Wed, Feb 12, 2025 at 01:23:09AM +0000, Kieran Kunhya via ffmpeg-devel
> wrote:
> > Is this a joke?
>
> no
>
> It follows up on Jean Baptistes request here:
> https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-August/312915.html
>
> | But it's not a library in that repository, like swscale, swresample or
> similar libraries.
> | If it was, with an API, it would be trivial to add support to this
> optional library as an FFmpeg module, and noone who complain.
>
> So the GSoC contributor would make this change, and then noone will
> complain.
>
> The GSoC contributor will just need precisse instructions so everyone
> will be ok and noone wil complain.
>
> thx
>
> [...]
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
If it's a library outside of FFmpeg, then you are welcome to submit it to
another SDR related Gsoc organisation. By definition your SDR lib is not
part of FFmpeg.
Kieran
>
_______________________________________________
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".
prev parent reply other threads:[~2025-02-12 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:21 Michael Niedermayer
2025-02-12 1:23 ` Kieran Kunhya via ffmpeg-devel
2025-02-12 2:11 ` Michael Niedermayer
2025-02-12 2:17 ` Kieran Kunhya via ffmpeg-devel [this message]
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='CABGuwE=kCnHMnWEyGJKxCV=nPC7=BPtjOM=+mdWhFHHbhyhg1g@mail.gmail.com' \
--to=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