From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
Sadiya Kazi <sadiyakazi@google.com>,
brendanhiggins@google.com, davidgow@google.com,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org
Subject: Re: New theme - Alabaster for Kernel Documentation
Date: Thu, 19 Jan 2023 14:55:18 -0700 [thread overview]
Message-ID: <87edrq6vg9.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230119214646.nquwprfswdckwexw@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> On Thu, Jan 19, 2023 at 02:29:21PM -0700, Jonathan Corbet wrote:
>> Akira Yokosawa <akiyks@gmail.com> writes:
>>
>> > Konstantin, would it be possible for you to add "DOCS_THEME=sphinx_rtd_theme"
>> > for the "latest" kernel documentation builds until the new default theme
>> > becomes good enough for most people? That is if Jon agrees.
>> > For the "next" builds, alabaster theme should be OK, and easier for us to
>> > compare the two themes.
>>
>> I'd prefer to avoid this if possible. In the end, though, what
>> kernel.org does isn't my decision, of course...
>
> Something I've considered is to have /latest/ show the latest mainline
> *released* mainline, while /rc/ would show the latest rc. So, we'd have three
> distinct movable targets:
>
> docs.kernel.org - latest mainline release (same as kernel.org/doc/html/latest/)
> docs.kernel.org/next/ - linux-next
> docs.kernel.org/rc/ - latest rc
>
> Would that be acceptable as a solution?
I think we've miscommunicated somewhere. What I don't like is the idea
of building the mainline docs with a non-default HTML theme.
A "latest -rc" build could be a nice thing, though :)
Thanks,
jon
next prev parent reply other threads:[~2023-01-19 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 4:25 New theme - Alabaster for Kernel Documentation Sadiya Kazi
2023-01-19 4:00 ` Akira Yokosawa
2023-01-19 21:29 ` Jonathan Corbet
2023-01-19 21:46 ` Konstantin Ryabitsev
2023-01-19 21:55 ` Jonathan Corbet [this message]
2023-01-19 22:02 ` Konstantin Ryabitsev
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=87edrq6vg9.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=konstantin@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=sadiyakazi@google.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox