git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/6] fix broken links in Documentation/
Date: Thu, 20 Apr 2017 16:32:04 -0400	[thread overview]
Message-ID: <20170420203203.xlbajdfzy7gp3hj3@sigill.intra.peff.net> (raw)

I've been looking at running an automated link-checker on git-scm.com.
But as it hosts HTML rendered from our Documentation/ directory, it
inherits any broken links that we have here. :)

This series fixes all the issues I could find.

  [1/6]: doc: use https links to avoid http redirect
  [2/6]: doc: replace or.cz gitwiki link with git.wiki.kernel.org
  [3/6]: gitcore-tutorial: update broken link
  [4/6]: docs/archimport: quote sourcecontrol.net reference
  [5/6]: docs/bisect-lk2009: update nist report link
  [6/6]: docs/bisect-lk2009: update java code conventions link

 Documentation/git-archimport.txt                 |  2 +-
 Documentation/git-bisect-lk2009.txt              | 14 +++++++-------
 Documentation/git-tools.txt                      |  2 +-
 Documentation/gitcore-tutorial.txt               |  2 +-
 Documentation/gitweb.conf.txt                    |  4 ++--
 Documentation/howto/rebuild-from-update-hook.txt |  4 ++--
 6 files changed, 14 insertions(+), 14 deletions(-)

-Peff

             reply	other threads:[~2017-04-20 20:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 20:32 Jeff King [this message]
2017-04-20 20:32 ` [PATCH 1/6] doc: use https links to avoid http redirect Jeff King
2017-04-20 20:32 ` [PATCH 2/6] doc: replace or.cz gitwiki link with git.wiki.kernel.org Jeff King
2017-04-20 20:33 ` [PATCH 3/6] gitcore-tutorial: update broken link Jeff King
2017-04-20 20:34 ` [PATCH 4/6] docs/archimport: quote sourcecontrol.net reference Jeff King
2017-04-20 20:35 ` [PATCH 5/6] docs/bisect-lk2009: update nist report link Jeff King
2017-04-20 20:35 ` [PATCH 6/6] docs/bisect-lk2009: update java code conventions link Jeff King

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=20170420203203.xlbajdfzy7gp3hj3@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    /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).