Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges
Date: Wed, 4 Jun 2025 16:51:29 +0200
Message-ID: <20250604145129.GS29660@pb2> (raw)
In-Reply-To: <CABGuwEmr62HoKVWS=uotyzetA75vdvuf9PHx__qYZeqaFY578g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

Hi

On Tue, Jun 03, 2025 at 11:38:11PM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> >
> > all members of fflabs where aware of it as i asked about the license
> > situation it in the private
> > fflabs IRC channel. I asked there because fflabs/jb has a lawyer
> >
> 
> Do you understand that the lawyer of FFlabs represents the interests of
> FFlabs and does not represent the interests of FFmpeg?

I understand that if i hire a lawyer, he would represent my interrests
If i ask SPI (which i did as well), they would represent SPI interrests

FFmpeg cannot hire a lawyer. So its easy to complain that it didnt

FFlabs depends on FFmpeg so its interrests in terms of FFmpeg complying
to all laws should be aligned here

And you are at the same level here, you can ask any lawyer you want.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2025-06-04 14:51 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 [this message]
2025-06-04 15:00             ` Kieran Kunhya via ffmpeg-devel
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=20250604145129.GS29660@pb2 \
    --to=michael@niedermayer.cc \
    --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