list mirror (unofficial, one of many)
 help / color / Atom feed
From: Jeff King <>
Subject: [PATCH 3/6] gitcore-tutorial: update broken link
Date: Thu, 20 Apr 2017 16:33:49 -0400
Message-ID: <> (raw)
In-Reply-To: <>

The slides for the Linux-mentoring presentation are no
longer available. Let's point to the wayback version of the
page, which works.

Note that the referenced diagram is also available on page
15 of [1]. We could link to that instead, but it's not clear
from the URL scheme ("uploads") whether it's going to stick
around forever.


Signed-off-by: Jeff King <>
TBH, I'm not sure this diagram is actually showing anything all that
useful, and maybe the paragraph could be re-worded, or a better diagram
found. I restricted myself here to a technical fix for the broken link,
but I'd be fine with somebody taking a more editorial pass.

 Documentation/gitcore-tutorial.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index 3a0ec8c53..7577f27ec 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -1429,7 +1429,7 @@ Although Git is a truly distributed system, it is often
 convenient to organize your project with an informal hierarchy
 of developers. Linux kernel development is run this way. There
 is a nice illustration (page 17, "Merges to Mainline") in
-[Randy Dunlap's presentation].
+[Randy Dunlap's presentation].
 It should be stressed that this hierarchy is purely *informal*.
 There is nothing fundamental in Git that enforces the "chain of

  parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 20:32 [PATCH 0/6] fix broken links in Documentation/ Jeff King
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 gitwiki link with Jeff King
2017-04-20 20:33 ` Jeff King [this message]
2017-04-20 20:34 ` [PATCH 4/6] docs/archimport: quote 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 publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

Archives are clonable:
	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox