All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jonathan Corbet <corbet@lwn.net>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org
Subject: Re: rst htmldocs on kernel.org
Date: Tue, 16 Aug 2016 10:24:56 +0200	[thread overview]
Message-ID: <20160816082456.GB9846@wunner.de> (raw)
In-Reply-To: <20160815162115.314690b7@lwn.net>

Hi Jonathan,

[+cc Konstantin]

On Mon, Aug 15, 2016 at 04:21:15PM -0600, Jonathan Corbet wrote:
> On Thu, 11 Aug 2016 21:13:29 +0200 Lukas Wunner <lukas@wunner.de> wrote:
> > not sure if this is already on your radar or if you're at all the
> > right person to contact, but I just noticed that the gpu htmldocs
> > are gone from https://www.kernel.org/doc/htmldocs/gpu/
> > 
> > Actually all the rst-formatted docs are missing. It would be great
> > if they could be reinstated so as to fix all the now dangling
> > hyperlinks out there...
> 
> I agree it would be good to get the new docs there.  Doing so in a way
> that avoids breaking links could prove hard, though.
> 
> I've (finally) sent off a note to Konstantin to see what can be done.

It occured to me only after sending you the above e-mail that
I should rather have e-mailed webmaster@kernel.org, apologies
for bothering you with this.

As for broken links, it's probably sufficient to just make sure that
the above-quoted top level URL is functioning. This may be as simple
as an "apt-get install python-sphinx python-sphinx-rtd-theme" on the
machine generating the docs, assuming it's Debian, and/or copying
the results to the appropriate htdocs folder.

Thanks,

Lukas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-08-16  8:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 10:47 [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal
2016-08-11 10:47 ` [RFC 1/4] dma-buf/fence: kerneldoc: remove unused struct members Sumit Semwal
2016-08-11 10:47   ` Sumit Semwal
2016-08-11 10:47 ` [RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header Sumit Semwal
2016-08-11 10:47   ` Sumit Semwal
2016-08-12  8:44   ` Daniel Vetter
2016-08-12  8:44     ` Daniel Vetter
2016-08-11 10:47 ` [RFC 3/4] Documentation: move dma-buf documentation to rst Sumit Semwal
2016-08-11 10:47   ` Sumit Semwal
2016-08-11 11:47   ` Jani Nikula
2016-08-11 11:47     ` Jani Nikula
2016-08-11 12:31     ` Sumit Semwal
2016-08-11 11:58   ` Markus Heiser
2016-08-11 12:12     ` Markus Heiser
2016-08-11 12:12       ` Markus Heiser
2016-08-11 12:49     ` Sumit Semwal
2016-08-11 12:49       ` Sumit Semwal
2016-08-11 10:48 ` [RFC 4/4] Documentation/sphinx: link dma-buf rsts Sumit Semwal
2016-08-11 10:48   ` Sumit Semwal
2016-08-11 14:36 ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Jonathan Corbet
2016-08-11 19:13   ` rst htmldocs on kernel.org Lukas Wunner
2016-08-15 22:21     ` Jonathan Corbet
2016-08-16  8:24       ` Lukas Wunner [this message]
2016-08-12  6:35   ` [RFC 0/4] doc: dma-buf: sphinx conversion and cleanup Sumit Semwal
2016-08-12  6:35     ` Sumit Semwal
2016-08-12  8:38     ` Daniel Vetter
2016-08-12  8:38       ` Daniel Vetter

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=20160816082456.GB9846@wunner.de \
    --to=lukas@wunner.de \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.