From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: TianoCore-docs GitBook Documentation Process
Date: Fri, 11 Aug 2017 18:30:00 +0200 [thread overview]
Message-ID: <a8224bba-a988-1ad1-479c-9162e9941689@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7D5902E@ORSMSX113.amr.corp.intel.com>
On 07/10/17 18:43, Kinney, Michael D wrote:
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Saturday, July 8, 2017 2:36 PM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: edk2-devel@lists.01.org
>> Subject: Re: [edk2] TianoCore-docs GitBook Documentation Process
>> [...] I'd just like
>> to
>> understand what the most direct way is to get GitBook.com render
>> any
>> branch from either an official docs repo, or a personal docs
>> repo.
>
> I will do some experiments with these ideas.
I learned about two features related to branches:
- The set of branches to build can be configured on the book's settings
page (after setting up integration with github). This page also lets the
user select the branch for the default rendering.
- In order to view the rendering of a non-default branch (from the set
of branched configured above), simply append "/v/BRANCH_NAME" to the
default rendering URL (which is
"https://<username>.gitbooks.io/<book-name>/content"). This is explained
here:
https://help.gitbook.com/content/how-can-i-access-a-specific-version.html
It seems to work for me.
Thanks!
Laszlo
prev parent reply other threads:[~2017-08-11 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:37 TianoCore-docs GitBook Documentation Process Kinney, Michael D
2017-07-08 21:35 ` Laszlo Ersek
2017-07-10 16:43 ` Kinney, Michael D
2017-07-10 20:38 ` Laszlo Ersek
2017-07-11 15:21 ` Kinney, Michael D
2017-07-11 17:05 ` Laszlo Ersek
2017-07-11 17:15 ` Kinney, Michael D
2017-07-12 18:12 ` Kinney, Michael D
2017-08-11 16:30 ` 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=a8224bba-a988-1ad1-479c-9162e9941689@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