From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/Doxfyile: Refactor for maintainability
Date: Sun, 28 Apr 2024 23:46:18 +0200
Message-ID: <20240428214618.GJ6420@pb2> (raw)
In-Reply-To: <Zi4gjtGjWk5EJXvB@andrews-2024-laptop.sayers>
[-- Attachment #1.1: Type: text/plain, Size: 880 bytes --]
Hi
On Sun, Apr 28, 2024 at 11:10:22AM +0100, Andrew Sayers wrote:
[...]
> Ping ?
>
> Michael, this is in response to your request[0]. I've queued up some more
> patches that depend on this and would help attract and retain developers (e.g.
> warning when you're looking at old documentation). What would be involved in
> getting this sort of thing on the website itself?
I dont have the time to review this
if you split the patch between updates to to comments and updates to teh actual
configuration this may make it easier to review to whoever does review it
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Many that live deserve death. And some that die deserve life. Can you give
it to them? Then do not be too eager to deal out death in judgement. For
even the very wise cannot see all ends. -- Gandalf
[-- 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:[~2024-04-28 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 17:03 Andrew Sayers
2024-04-28 10:10 ` Andrew Sayers
2024-04-28 21:46 ` Michael Niedermayer [this message]
2024-04-29 8:53 ` Andrew Sayers
2024-04-30 17:26 ` Michael Niedermayer
2024-05-01 0:08 ` Andrew Sayers
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=20240428214618.GJ6420@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