qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [qemu-web PATCH] documentation: update links to readthedocs
Date: Mon, 3 Feb 2020 14:21:52 +0100	[thread overview]
Message-ID: <ef53558f-4126-2144-19bf-8955a2184743@redhat.com> (raw)
In-Reply-To: <CAFEAcA8ai76afSyMhFr0u4fMtD7iR3mAi3EUsGA1-NBZ5bCeOg@mail.gmail.com>

On 03/02/2020 13.44, Peter Maydell wrote:
> On Mon, 3 Feb 2020 at 12:38, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Mon, 3 Feb 2020 at 12:12, Thomas Huth <thuth@redhat.com> wrote:
>>> Ok. Should we then just remove https://www.qemu.org/documentation/
>>> completely and make the "Documentation" link in the "menu" point
>>> directly to https://www.qemu.org/docs/master/ instead?
>>> We could simply mention the Wiki in docs/index.html.in, too, I think?
>>
>> I think I'd keep the current documentation/ page for now
>> (we probably don't want index.html.in to refer to the
>> developer documentation or the git tree).
> 
> There's also a 'Manual' link in the footer thingy on every page
> which currently goes to https://qemu.weilnetz.de/qemu-doc.html;
> since we already have a 'Documentation' link to
> https://www.qemu.org/documentation in the footer, I guess the
> simplest thing there is to just delete the 'Manual' line.

I've now sent a patch ("[qemu-web PATCH] Update the documentation
links to point to our generated docs"), but I decided to keep the
"Manual" link there so that the footer does not look so empty (but
of course I've updated the link to the new location instead).

 Thomas




  parent reply	other threads:[~2020-02-03 13:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:35 [qemu-web PATCH] documentation: update links to readthedocs Alex Bennée
2020-01-14 11:04 ` Stefan Hajnoczi
2020-01-14 11:11 ` Thomas Huth
2020-01-15 11:10   ` Stefan Hajnoczi
2020-01-15 11:56     ` Alex Bennée
2020-01-15 12:01       ` Daniel P. Berrangé
2020-01-20 10:16         ` Stefan Hajnoczi
2020-01-20 10:31     ` Peter Maydell
2020-02-03 11:46     ` Peter Maydell
2020-02-03 11:54       ` Thomas Huth
2020-02-03 12:07         ` Peter Maydell
2020-02-03 12:12           ` Thomas Huth
2020-02-03 12:38             ` Peter Maydell
2020-02-03 12:44               ` Peter Maydell
2020-02-03 12:46                 ` Thomas Huth
2020-02-03 13:21                 ` Thomas Huth [this message]
2020-02-05 10:28       ` Stefan Hajnoczi

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=ef53558f-4126-2144-19bf-8955a2184743@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).