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] Cherry picks vs merges
Date: Wed, 4 Jun 2025 16:00:13 +0100
Message-ID: <CABGuwEmhr_ZB7cnOo11-nf5A2mFmMooehBoPLhwBAg3w3Zhf7g@mail.gmail.com> (raw)
In-Reply-To: <20250604145129.GS29660@pb2>
> FFlabs depends on FFmpeg so its interrests in terms of FFmpeg complying
> to all laws should be aligned here
Interesting, so the person that complains about FFlabs having too much
corporate control over FFmpeg is now ok to assume FFlabs legal opinion
"align[ing]" with 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".
next prev parent reply other threads:[~2025-06-04 15:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 15:22 Michael Niedermayer
2025-06-01 17:12 ` Kieran Kunhya via ffmpeg-devel
2025-06-01 17:27 ` James Almer
2025-06-01 19:23 ` Michael Niedermayer
2025-06-01 19:48 ` compn
2025-06-01 20:01 ` James Almer
2025-06-01 21:31 ` Michael Niedermayer
2025-06-02 4:46 ` Vittorio Giovara
2025-06-02 15:05 ` Michael Niedermayer
2025-06-02 7:41 ` Marton Balint
2025-06-02 8:23 ` softworkz .
2025-06-02 15:28 ` Michael Niedermayer
2025-06-02 15:57 ` Kieran Kunhya via ffmpeg-devel
2025-06-04 15:20 ` compn
2025-06-01 21:55 ` Kieran Kunhya via ffmpeg-devel
2025-06-02 4:36 ` Baptiste Coudurier
2025-06-02 15:38 ` Rémi Denis-Courmont
2025-06-03 13:09 ` Michael Niedermayer
2025-06-03 22:38 ` Kieran Kunhya via ffmpeg-devel
2025-06-04 14:51 ` Michael Niedermayer
2025-06-04 15:00 ` Kieran Kunhya via ffmpeg-devel [this message]
2025-06-04 15:35 ` Rémi Denis-Courmont
2025-06-04 18:06 ` Tomas Härdin
2025-06-04 20:42 ` Baptiste Coudurier
2025-06-04 22:41 ` 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=CABGuwEmhr_ZB7cnOo11-nf5A2mFmMooehBoPLhwBAg3w3Zhf7g@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