public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Michael Kinney <michael.d.kinney@intel.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Stephano Cetola <stephano.cetola@intel.com>
Subject: gitbook.com integration doesn't seem to work
Date: Fri, 30 Aug 2019 14:32:51 +0200	[thread overview]
Message-ID: <275f3a9f-85d9-7585-fbe6-4cff8e62fdda@redhat.com> (raw)

Hi Mike,

I've written three patches for the C Coding Standards document (for
addressing TianoCore#607), and pushed them to my personal repo:

  https://github.com/lersek/edk2-CCodingStandardsSpecification

on branch

  spurious_assign_bz_607

The latest commit is presently commit 66b44ceed69d ("must comment: add
rule for documenting spurious variable assignments", 2019-08-30).


On GitBooks.com, I had created a personal fork of the CCS about two
years ago, and I had set up the integration with my GitHub.com
repository. Back then, the integration worked fine, and when I posted
some CCS patches, I was able to link rendered views of the modified
pages in the cover letter. See for example the following posting:

  [edk2] [edk2-CCodingStandardsSpecification PATCH 0/2]
  improvements related to line wrapping

  https://lists.01.org/pipermail/edk2-devel/2017-August/013165.html

Specifically, the URL

  https://lersek.gitbooks.io/laszlo-s-fork-of-the-edk-ii-c-coding-standards-sp/content/v/line_wrapping/

continues to work to this day, with the "line_wrapping" part
corresponding to the branch name from two years ago.


Now, the problem is that I seem unable to get a rendered view of my new
branch, called "spurious_assign_bz_607". If I simply replace
"line_wrapping" with the new branch name in the URL above, I get "Page
Not Found".

In my "Settings" dialog on GitBooks.com:

  https://legacy.gitbook.com/book/lersek/laszlo-s-fork-of-the-edk-ii-c-coding-standards-sp/settings

I have verified that GitBooks.com sees the new branch, and that the
GitBooks.com and GitHub.com repositories are "in sync":

  https://legacy.gitbook.com/book/lersek/laszlo-s-fork-of-the-edk-ii-c-coding-standards-sp/settings/github

Furthermore, the "update count" at

  https://legacy.gitbook.com/book/lersek/laszlo-s-fork-of-the-edk-ii-c-coding-standards-sp/activity

has increased from "4" to "5", which is valud -- but then the activity
log for the specific branches is questionable:

- when I select the master branch, while the activity log references the
  latest commit on master correctly (d096859f15b9), it labels it "12
  hours ago" -- which is bogus, as that patch was commited on
  2019-Apr-18,

- when I select the new branch, called "spurious_assign_bz_607" -- note:
  I *can* select it --, I get "Nothing to show! There is currently no
  updates on this branch".

So basically the integration with github.com seems to have fallen apart.

Has anyone else seen this? How can we fix it?

I don't feel comfortable posting CCS patches without verifying a
rendered HTML view on GitBooks.com.

Thanks!
Laszlo

                 reply	other threads:[~2019-08-30 12:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=275f3a9f-85d9-7585-fbe6-4cff8e62fdda@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