All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Andrea Stacchiotti <andreastacchiotti@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] doc: git-htmldocs.googlecode.com is no more
Date: Wed, 22 Jun 2016 16:06:08 -0400	[thread overview]
Message-ID: <20160622200607.GD1697@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq60t1noon.fsf@gitster.mtv.corp.google.com>

On Wed, Jun 22, 2016 at 10:00:56AM -0700, Junio C Hamano wrote:

> Peff suggested to use the github pages that are connected to the
> "git" org, and helped its initial set-up.  When I update the
> prebuilt docs, in addition to the listed locations, I also push to
> the gh-pages branch of https://github.com/git/htmldocs repository
> and the result appears in https://git.github.io/htmldocs/git.html
> 
> Even though we do have index.html -> git.html, gh-pages does not
> seem to let you follow it, so you need to start from git.html, and I
> suspect that it is why the below says "I wasn't able to find it" for
> (5).

Yeah, I looked into this a little back then, and I think it is simply
that the Pages builder does not handle symlinks at all. You could push
out index.html as a true copy rather than a symlink, but I think just
pointing to "git.html" as the entry page of the site is reasonable, too
(we could even make index.html a true overview page later if we want).

> So perhaps list both?  I do not know how beefy repo.or.cz is, or how
> well connected it is to the rest of the world, but if I have to pick
> only one, I'd feel safer if we didn't have to exploit the "blob_plain/:"
> backdoor.

Beefiness aside, the GitHub version will be served out of a CDN, which
means it should perform way better for the user, as it will often get
served from a geographically local cache.

-Peff

  parent reply	other threads:[~2016-06-22 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <146652690896.29270.13813898006180324611.reportbug@duelitri>
2016-06-22  2:41 ` [PATCH] doc: git-htmldocs.googlecode.com is no more Jonathan Nieder
2016-06-22 17:00   ` Junio C Hamano
2016-06-22 17:38     ` [PATCH v2] " Jonathan Nieder
2016-06-22 20:06     ` Jeff King [this message]
2016-06-22 19:00   ` [PATCH] " Eric Wong
2016-06-22 19:02     ` Junio C Hamano
2016-06-22 21:48       ` Eric Wong
2016-06-23  7:04       ` Matthieu Moy
2016-06-24 19:48         ` Junio C Hamano
2016-06-28 18:03         ` Junio C Hamano

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=20160622200607.GD1697@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=andreastacchiotti@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.