From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] [ffmpeg-web] branch master updated. 42a0288 web/download: Add FFmpeg 5.1
Date: Sat, 23 Jul 2022 16:53:53 +0200
Message-ID: <20220723145353.GS2088045@pb2> (raw)
In-Reply-To: <77bc86af-c465-b615-bc6d-5e41b56a0d71@gyani.pro>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
On Sat, Jul 23, 2022 at 09:55:15AM +0530, Gyan Doshi wrote:
>
>
> On 2022-07-23 02:16 am, Michael Niedermayer wrote:
> > On Sat, Jul 23, 2022 at 12:06:29AM +0530, Gyan Doshi wrote:
> > > Is the News entry forthcoming?
> > sounds like you want to write the news entry?
>
> Not exactly. For 4.3, it was never posted. I did it 10 months after the
> release.
> So just checking if it's on your radar.
I hoped someone who is good at english news entries and who enjoys writing
them will do it :-)
I may have underestimated the importance of a news entry. Only after you
reminded me it became obvious that our first LTS release should have a news
entry
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates
[-- 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".
next prev parent reply other threads:[~2022-07-23 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220722183051.8E5F568B701@ffbox0-bg.mplayerhq.hu>
2022-07-22 18:36 ` Gyan Doshi
2022-07-22 20:46 ` Michael Niedermayer
2022-07-23 4:25 ` Gyan Doshi
2022-07-23 14:53 ` Michael Niedermayer [this message]
2022-07-23 14:55 ` James Almer
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=20220723145353.GS2088045@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