From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] doc: add spi.txt
Date: Tue, 7 Nov 2023 23:01:06 +0100 (CET)
Message-ID: <NifnQ5t--3-9@lynne.ee> (raw)
In-Reply-To: <20231107201647.GR3543730@pb2>
Nov 7, 2023, 21:17 by michael@niedermayer.cc:
> On Thu, Oct 19, 2023 at 03:29:57AM +0200, Lynne wrote:
>
>> Oct 19, 2023, 00:15 by stefasab@gmail.com:
>>
>> > On date Wednesday 2023-10-18 23:46:48 +0200, Stefano Sabatini wrote:
>> >
>> >> On date Tuesday 2023-10-17 14:41:00 +0200, epirat07@gmail.com wrote:
>> >>
>> > [...]
>> >
>> >> > IMO this would be much more discoverable on the website, it would
>> >> > never occur to me to look for such information in the FFmpeg source
>> >> > tree doc folder.
>> >>
>> >> I'm fine with either, I'll let Michael decide the final target repository.
>> >>
>> >
>> > OTOH more visibility for something which is not yet very well defined
>> > is not necessarily good, I'd move that to the website only when/iff
>> > the process is more consolidated.
>> >
>>
>> I think since it's not related to code, it should go on the website,
>> if only to keep the repo clean.
>>
>
> where would you suggest to put it on the wegbpage ?
> the webpage is html, i dont think we have .txt on the webpage
>
> thx
>
Under More->SPI or Developers->SPI?
You could copy paste some other page to use as boilerplate
and paste the doc on there?
_______________________________________________
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-11-07 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 22:49 Michael Niedermayer
2023-10-16 4:34 ` Lynne
2023-10-17 7:29 ` Stefano Sabatini
2023-10-17 12:41 ` epirat07
2023-10-18 21:46 ` Stefano Sabatini
2023-10-18 22:15 ` Stefano Sabatini
2023-10-19 1:29 ` Lynne
2023-11-07 20:16 ` Michael Niedermayer
2023-11-07 22:01 ` Lynne [this message]
2023-10-17 7:22 ` Stefano Sabatini
2023-11-08 11:35 ` Alexander Strasser
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=NifnQ5t--3-9@lynne.ee \
--to=dev@lynne.ee \
--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