From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] Left FFmpeg; starting Librempeg
Date: Thu, 7 Dec 2023 11:52:27 +0100
Message-ID: <CAPYw7P7=X=tHMdMReCtyvoOYwfAyMD-QhQDa9q9J=gNn58dE=A@mail.gmail.com> (raw)
In-Reply-To: <Nl2aURI--3-9@lynne.ee>
On Thu, Dec 7, 2023 at 10:27 AM Lynne <dev@lynne.ee> wrote:
> Dec 7, 2023, 09:51 by onemda@gmail.com:
>
> > On Thu, Dec 7, 2023 at 9:23 AM Lynne <dev@lynne.ee> wrote:
> >
> >> Dec 6, 2023, 21:27 by onemda@gmail.com:
> >>
> >> > Today, effectively immediately, I officially Ieft the FFmpeg project.
> >> >
> >> > For new
> >> >
> decoders/encoders/muxers/demuxers/filters/fixes/speedups/tests/cleanups
> >> > etc. look at Librempeg project on github, source code will appear soon
> >> > there.
> >> >
> >>
> >> Calm down, there's no need to leave over such silly reasons. Tests
> >> can wait, and someone else can add them.
> >> Besides, I need someone to review my FFT patches which I plan to post in
> >> a few hours, and there's still the AC-4 decoder that I'll help you
> finish
> >> up.
> >> Take a few days off if you have to, log back into IRC and we'll talk it
> >> through?
> >>
> >
> > Sorry to disappoint you but that hit just top of iceberg.
> >
> > For FFT/RDFT x86 improvements and testing you can send PR to Librempeg
> > project directly.
> >
>
> I think it would be easier to just work together here.
> If you're unhappy with the rules, like requiring patches to sit
> on the ML for review for 3 days before pushing, even if the code is your
> own,
> we can change that.
> There's nothing that cannot be fixed.
>
Its over. sooner you accept that its better.
Already removed libpostproc cruft, and couple others (sonic) are planned
for removal too.
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2023-12-07 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 20:26 Paul B Mahol
2023-12-07 8:22 ` Lynne
2023-12-07 8:51 ` Paul B Mahol
2023-12-07 9:26 ` Lynne
2023-12-07 10:52 ` Paul B Mahol [this message]
2023-12-07 11:38 ` Lynne
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='CAPYw7P7=X=tHMdMReCtyvoOYwfAyMD-QhQDa9q9J=gNn58dE=A@mail.gmail.com' \
--to=onemda@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