Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] statictrac, trac and caching
Date: Sun, 15 Jun 2025 12:03:01 -0500
Message-ID: <CAAhd_PUmbO2MxaMd0QE-EdK5Lxr4kB9aNAJi_XMkPmEnJgreXQ@mail.gmail.com> (raw)
In-Reply-To: <20250615165330.GZ29660@pb2>

Hello Michael,

On Sun, Jun 15, 2025 at 11:53 AM Michael Niedermayer
<michael@niedermayer.cc> wrote:
> The wiki has the huge advantage that people can edit it easily
>
> Editing the docs people have to do a git checkout, edit a file
> with an editor, make a git commit read patch submission rules
> submit a patch to ML or forge.
>
> Thats alot stumbling blocks thrown in ones way
I agree, I don't think or mean to throw away the wiki.
But more along the lines was thinking of upstreaming some of the more
mature examples and information there.
For example, this page is already covered in the docs:
https://trac.ffmpeg.org/wiki/HowToExtractAndRemoveClosedCaptions

I guess framed the thought in a too general fashion.
Maybe a little tidying is all I was wanting and is irrelevant of this
conversation so I'll compartmentalize it for later.

> > There are some good examples and information there that seem to me can
> > be crystallized into plain old texi.
> > While I'm neutral about Trac I think in a sense this could also help
> > in the sense of reducing server load for this somewhat static content.
>
> yesterdays incident had like ~40k accesses on teh same file.
> So moving 99% of content out of trac would not have helped if
> that file was in teh 1%

That's a fair and valid point.

Thank you,
_______________________________________________
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-15 17:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 13:35 Michael Niedermayer
2025-06-15 13:42 ` Michael Niedermayer
2025-06-15 13:53   ` Derek Buitenhuis
2025-06-15 15:58     ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer
2025-06-15 16:17       ` Derek Buitenhuis
2025-06-15 14:45   ` [FFmpeg-devel] " James Almer
2025-06-15 16:13     ` [FFmpeg-devel] Forensics Was: " Michael Niedermayer
2025-06-15 18:45   ` Michael Niedermayer
2025-06-15 14:53 ` [FFmpeg-devel] " James Almer
2025-06-15 15:57   ` Kacper Michajlow
2025-06-15 16:06     ` Marth64
2025-06-15 16:53       ` Michael Niedermayer
2025-06-15 17:03         ` Marth64 [this message]
2025-06-15 16:48     ` Michael Niedermayer
2025-06-15 19:05     ` Michael Niedermayer
2025-06-15 16:28   ` 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=CAAhd_PUmbO2MxaMd0QE-EdK5Lxr4kB9aNAJi_XMkPmEnJgreXQ@mail.gmail.com \
    --to=marth64@proxyid.net \
    --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