public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Rebecca Cran <rebecca@bluestop.org>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: edk2-docs hosted on legacy gitbook site - is migration to new version planned?
Date: Tue, 11 Jun 2019 17:55:21 +0200	[thread overview]
Message-ID: <19c587a1-8bd7-e150-4e0b-90898955634a@redhat.com> (raw)
In-Reply-To: <a2183f94-58c9-ae46-c428-e2538f7dc91b@bluestop.org>

Hi,

On 06/11/19 16:29, Rebecca Cran wrote:
> I noticed the edk2-docs are hosted on the *legacy* gitbook.com site, at
> https://legacy.gitbook.com/@edk2-docs .
> 
> Are there any plans to migrate to the new version
> (https://docs.gitbook.com/getting-started/migrating-from-the-previous-version)?

if I click the "HTML" links in the Wiki article at:

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Specifications

for example the "HTML" link for the Build Spec, I land at:

https://edk2-docs.gitbooks.io/edk-ii-build-specification/content/v/release/1.28/

This is the "new version" of gitbook, right?


I certainly have the link <https://legacy.gitbook.com/@edk2-docs> in my
browser history as well, but I'm not sure where it is still referenced
from... Ah wait, after grepping a local clone of the edk2 wiki, the
following article does have a reference:

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Documents

under caption "EDK II Documents on GitBook". I guess that link should be
updated, but I'm not sure what to. FWIW, if I just enter
<https://edk2-docs.gitbooks.io>, it redirects to
<https://legacy.gitbook.com/@edk2-docs> :/

Thanks
Laszlo


      reply	other threads:[~2019-06-11 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 14:29 edk2-docs hosted on legacy gitbook site - is migration to new version planned? rebecca
2019-06-11 15:55 ` Laszlo Ersek [this message]

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-list 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=19c587a1-8bd7-e150-4e0b-90898955634a@redhat.com \
    --to=devel@edk2.groups.io \
    /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