All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Jonathan Nieder <jrnieder@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: 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 19:00:18 +0000	[thread overview]
Message-ID: <20160622190018.GA786@dcvr.yhbt.net> (raw)
In-Reply-To: <20160622024151.GA20206@google.com>

Jonathan Nieder <jrnieder@gmail.com> wrote:
> I'd rather use an up-to-date https link for the rendered
> documentation, but I wasn't able to find one.  According to the 'todo'
> branch, prebuilt documentation is pushed to
> 
>  1. https://kernel.googlesource.com/pub/scm/git/git-htmldocs
>  2. git://repo.or.cz/git-htmldocs
>  3. somewhere on git.sourceforge.jp and git.sourceforge.net?
>  4. https://github.com/gitster/git-htmldocs
>  5. https://github.com/git/htmldocs

Just wondering, who updates
https://kernel.org/pub/software/scm/git/docs/
and why hasn't it been updated in a while?
(currently it says Last updated 2015-06-06 at the bottom)

I normally link people there since I would rather not advertise
for a commercial service.

  parent reply	other threads:[~2016-06-22 19:00 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     ` [PATCH] " Jeff King
2016-06-22 19:00   ` Eric Wong [this message]
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=20160622190018.GA786@dcvr.yhbt.net \
    --to=e@80x24.org \
    --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.