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: Mon, 10 Jul 2017 22:38:59 +0200 [thread overview]
Message-ID: <6d43e2dd-d795-3a84-0f15-9683e43d3bb6@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5A7D5902E@ORSMSX113.amr.corp.intel.com>
Hello Mike,
On 07/10/17 18:43, Kinney, Michael D wrote:
> Hi Laszlo,
>
> Thanks for the quick feedback on this content.
>
> Reponses included below, and I have already made some
> updates to the wiki based on your feedback.
thank you for the answers, they are very helpful. I'll highlight one thing:
> The GitBook
> integration with GitHub is actually a bidirectional sync, so I found
> it confusing to do edits from both sides. Also, an edit from the
> GitBook side does not follow the TianoCore patch/review process.
I did not miss the bidirectional arrow :) in the top diagram of
<https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore-Documents-GitBook-Overview>,
between "GitHub tianocore-docs" and "GitBook tianocore-docs". I was
wondering if the left-pointing arrow was an oversight :)
So apparently it's not. We'll have to be careful to avoid WYSIWYG
editing on GitBook.com (personally I'd like to avoid that even for my
forks too). I guess one way to stay safe is to remain logged out of the
GitHub & GitBook websites most of the time (which is how I've been
operating anyway).
Thanks!
Laszlo
next prev parent reply other threads:[~2017-07-10 20:37 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 [this message]
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
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=6d43e2dd-d795-3a84-0f15-9683e43d3bb6@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