git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kevin <ikke@ikke.info>
To: Mike Norman <mknorman@gmail.com>
Cc: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>,
	Scott Chacon <schacon@gmail.com>,
	Andrew Ardill <andrew.ardill@gmail.com>,
	git <git@vger.kernel.org>
Subject: Re: Links broken in ref docs.
Date: Wed, 31 Oct 2012 12:17:01 +0100	[thread overview]
Message-ID: <CAO54GHC-rBV-RnZ+69W8sROE+TOZ14t-D9Xq4PyEZNP7yLJnHA@mail.gmail.com> (raw)
In-Reply-To: <CAJr+XPH4MTg_F_YuT=R1mLVwOUYPB0US3w2mZ1+DDvrQV7vVfQ@mail.gmail.com>

Looks fixed here too

On Wed, Oct 31, 2012 at 12:30 AM, Mike Norman <mknorman@gmail.com> wrote:
> I just checked and the issue seems to be fixed! Clicked around on a
> bunch of previously broken links and they work!
>
> On Tue, Oct 30, 2012 at 3:38 AM, Holger Hellmuth (IKS)
> <hellmuth@ira.uka.de> wrote:
>> Am 30.10.2012 09:07, schrieb Mike Norman:
>>
>>> Not seen any recently. I'm guessing the dev is in the path of
>>> hurricane Sandy? (Not sarcasm, btw.)
>>
>>
>> Do you still see failures? I checked out the website just now and it seemed
>> to work flawlessly (at least the links I tried, could not find any Sharing
>> or Updating section). New design since I last visited, more end-user polish.
>>
>>

      reply	other threads:[~2012-10-31 11:17 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
     [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 [this message]

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=CAO54GHC-rBV-RnZ+69W8sROE+TOZ14t-D9Xq4PyEZNP7yLJnHA@mail.gmail.com \
    --to=ikke@ikke.info \
    --cc=andrew.ardill@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.de \
    --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).