From: Andrew Ardill <andrew.ardill@gmail.com>
To: Mike Norman <mknorman@gmail.com>
Cc: git <git@vger.kernel.org>, Scott Chacon <schacon@gmail.com>
Subject: Re: Links broken in ref docs.
Date: Mon, 22 Oct 2012 15:45:00 +1100 [thread overview]
Message-ID: <CAH5451nFf_SY4K2DS52vhP6VeXSmeikUrc0zy8HK3xmGgs+UGg@mail.gmail.com> (raw)
In-Reply-To: <CAJr+XPGm4djBh+vacG5Ff=Y6aYmWbcUXOV9x2jekgnsGsk4b-g@mail.gmail.com>
On 21 October 2012 18:31, Mike Norman <mknorman@gmail.com> wrote:
> Many links on scm-git.org/docs simply reload the page.
>
> For example, all of Sharing and Updating section simply reload the
> docs page. And tons others. Must be a broken link or routing problem.
> Repros on FF 14.0.1 and Chrome. Good luck!
>
Including Scott Chacon as he manages this site (to my knowledge).
Looking at the request, I am getting a 302:
Request URL:http://git-scm.com/docs/git-fetch
Request Method:GET
Status Code:302 Moved Temporarily
Maybe those pages are not done yet? That doesn't seem right as this is
simply the reference manual, but perhaps there is something else going
on here.
On another (related) note, the wayback machine has some very
interesting entries for the scm-git.org domain [1] and it seems the
/doc directory is not indexed at all. Is this on purpose?
Regards,
Andrew Ardill
[1] http://wayback.archive.org/web/*/http://git-scm.com/*
next prev parent reply other threads:[~2012-10-22 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 7:31 Links broken in ref docs Mike Norman
2012-10-22 4:45 ` Andrew Ardill [this message]
[not found] ` <CAJr+XPETQ2Jifns3_dfoB-sLLru2=Jkofb5RrBxLE4Fa9Aqp7A@mail.gmail.com>
2012-10-23 5:11 ` Scott Chacon
2012-10-30 8:04 ` Kevin
2012-10-30 8:07 ` Mike Norman
2012-10-30 10:38 ` Holger Hellmuth (IKS)
2012-10-30 23:30 ` Mike Norman
2012-10-31 11:17 ` Kevin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH5451nFf_SY4K2DS52vhP6VeXSmeikUrc0zy8HK3xmGgs+UGg@mail.gmail.com \
--to=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=mknorman@gmail.com \
--cc=schacon@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).