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] FFmpeg release 6.1 (SDR Plans)
Date: Thu, 21 Sep 2023 20:56:52 +0200
Message-ID: <20230921185652.GS8640@pb2> (raw)
In-Reply-To: <CABGuwE=3tr3C=NZmZiyDj39RJ64RQ50hWJFmt4xr9AvzDX_CRg@mail.gmail.com>


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

Hi

On Thu, Sep 21, 2023 at 05:33:54PM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Thu, Sep 21, 2023 at 5:21 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> > OTOH If a majority of people are against the SDR code at the time of
> > branching 6.1. Then i will make a separate release identical to 6.1 with
> > the SDR code and of course also provide security support
> 
> How on earth is it acceptable that you can publish your hobby project
> under the FFmpeg project name?

How on earth is this defamation acceptable?
In fact iam not even sure what you talk about.
FFmpeg is not a propriatery licensed project

It seems to me you are trying to rally your followers against me, with
these attacks, thats really lame IMHO
If you have real arguments, you can state them without these attacks


> You are of course welcome to publish SDR in a different project that
> is not FFmpeg.

> 
> I have been working on BIOS code recently but I haven't decided to
> create FFBIOS and put it in the main FFmpeg repo.

because doing so would make no sense, BIOS is unrelated to FFmpeg and
multimedia
But if you do, noone would attack you like you do, we would just
have a normal discussion about why you think this makes sense, and
i think you dont think that makes sense so we would agree that BIOS
doesnt belong in FFmpeg

If OTOH you would create something related, you could name it FFmpeg-<whatever>
nothing wrong here, other people do it to, github has 26300 hits for FFmpeg

If its something that has users, maintained, ... but is not accepted in
main FFmpeg. Sure we can list it on our download page too.

thx

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

The real ebay dictionary, page 1
"Used only once"    - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."

[-- 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".

  parent reply	other threads:[~2023-09-21 18:57 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 22:14 [FFmpeg-devel] FFmpeg release 6.1 Michael Niedermayer
2023-04-10 22:16 ` James Almer
2023-04-11  8:46 ` Neal Gompa
2023-09-19 17:18 ` Niklas Haas
2023-09-19 19:16   ` Michael Niedermayer
2023-09-19 21:58     ` Lynne
2023-09-20  0:38       ` Neal Gompa
2023-09-20  2:24         ` Xiang, Haihao
2023-09-20 17:24       ` Michael Niedermayer
2023-09-20 17:43         ` Kieran Kunhya
2023-09-20 18:10           ` Michael Niedermayer
2023-09-20 22:47             ` Kieran Kunhya
2023-09-21  3:19               ` Jean-Baptiste Kempf
2023-09-21 12:51               ` Michael Niedermayer
2023-09-20 12:47     ` Niklas Haas
2023-09-20 18:00       ` Michael Niedermayer
2023-09-21 11:46     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-09-21 16:21 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Michael Niedermayer
2023-09-21 16:33   ` Kieran Kunhya via ffmpeg-devel
2023-09-21 17:16     ` Nicolas George
2023-09-21 18:14       ` Vittorio Giovara
2023-09-21 18:19         ` Nicolas George
2023-09-21 18:47           ` Vittorio Giovara
2023-09-21 18:51             ` Nicolas George
2023-09-21 18:54               ` Vittorio Giovara
2023-09-21 19:04                 ` Nicolas George
2023-09-21 19:08                   ` Paul B Mahol
2023-09-26 18:14                     ` Nicolas George
2023-09-21 19:18                   ` Vittorio Giovara
2023-09-21 19:37                     ` Nicolas George
2023-09-21 19:44                       ` Paul B Mahol
2023-09-21 18:56     ` Michael Niedermayer [this message]
2023-09-26 19:59       ` Rémi Denis-Courmont
2023-09-21 16:39   ` Paul B Mahol
2023-09-22 13:55   ` Gijs Peskens
2023-09-22 16:32     ` Michael Niedermayer
2023-09-23  6:49       ` Neal Gompa
2023-09-23 10:55         ` Michael Niedermayer
2023-09-23 23:31           ` Neal Gompa
2023-09-24  9:12         ` Nicolas George
2023-09-24 11:56           ` Paul B Mahol
2023-09-24 12:17             ` Nicolas George
2023-09-24 17:33               ` Paul B Mahol
2023-09-24 17:45                 ` [FFmpeg-devel] libavdevice (was: FFmpeg release 6.1 (SDR Plans)) Nicolas George
2023-09-24 17:49                   ` Paul B Mahol
2023-09-24 17:54                     ` Nicolas George
2023-09-24 18:05                       ` Paul B Mahol
2023-09-24 18:09                         ` Nicolas George
2023-09-25 11:20                           ` Paul B Mahol
2023-09-26 18:12                             ` Nicolas George
2023-09-25  8:24                 ` [FFmpeg-devel] FFmpeg release 6.1 (SDR Plans) Kieran Kunhya
2023-09-26 20:17         ` Rémi Denis-Courmont

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=20230921185652.GS8640@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