From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/plans: add a file to list approved projects
Date: Thu, 18 Aug 2022 19:26:41 +0200
Message-ID: <b8e170d0-3db6-4e17-8d19-dabc9fcfb214@beta.fastmail.com> (raw)
In-Reply-To: <20220817214932.42351-1-george@nsup.org>
n Wed, 17 Aug 2022, at 23:49, Nicolas George wrote:
> doc/plans.md | 6 ++++++
> 1 file changed, 6 insertions(+)
Those plans files become outdated very quickly and are often not maintained.
Or they become infinite unicorn-wishlist things.
Or they become a blocking task for the project.
I have NO opinion on AVWriter, but just show the API and documentation before implementing it.
Once people agree on the API need and form, just implement it, I don't see the need for a plans.md file for that.
--
Jean-Baptiste Kempf - President
+33 672 704 734
_______________________________________________
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-08-18 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 21:49 Nicolas George
2022-08-17 21:49 ` [FFmpeg-devel] [PATCH 2/2] doc/plans: add AVWriter Nicolas George
2022-08-18 6:40 ` Paul B Mahol
2022-08-18 17:23 ` Jean-Baptiste Kempf
2022-08-22 14:55 ` Leo Izen
2022-08-22 14:59 ` Nicolas George
2022-08-18 6:49 ` [FFmpeg-devel] [PATCH 1/2] doc/plans: add a file to list approved projects Anton Khirnov
2022-08-18 17:26 ` Jean-Baptiste Kempf [this message]
2022-08-19 16:01 ` Nicolas George
2022-08-19 16:08 ` Jean-Baptiste Kempf
2022-08-22 12:43 ` Nicolas George
2022-08-22 14:42 ` Jean-Baptiste Kempf
2022-08-22 15:01 ` Nicolas George
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=b8e170d0-3db6-4e17-8d19-dabc9fcfb214@beta.fastmail.com \
--to=jb@videolan.org \
--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