git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v3 2/2] doc: remove references to gittutorial-2

From
Julia Evans via GitGitGadget <gitgitgadget@gmail.com>
Date
Oct 26, 2026, 13:52 UTC
Message-ID
<0a42345cecec10bd32ae3db1a699452b164a2f25.1793022742.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.2241.v3.git.1793022742.gitgitgadget@gmail.com>
From: Julia Evans <julia@jvns.ca>

Redirect folks to `gitdatamodel` instead, since every time it's referenced the intent is to explain objects, references, blobs, etc.

The update to `gittutorial` isn't very carefully thought through since we're planning to delete that entire document anyway. It's just there to maintain some internal consistency.

Signed-off-by: Julia Evans <julia@jvns.ca>
---
 Documentation/MyFirstObjectWalk.adoc |  2 +-
 Documentation/git.adoc               |  2 +-
 Documentation/gitcore-tutorial.adoc  |  1 -
 Documentation/gitcvs-migration.adoc  |  2 +-
 Documentation/gitglossary.adoc       |  1 -
 Documentation/gittutorial.adoc       | 23 +++++------------------
 command-list.txt                     |  1 -
 7 files changed, 8 insertions(+), 24 deletions(-)
diff --git a/Documentation/MyFirstObjectWalk.adoc b/Documentation/MyFirstObjectWalk.adoc
index 413a9fdb05..76e635b93a 100644
--- a/Documentation/MyFirstObjectWalk.adoc
+++ b/Documentation/MyFirstObjectWalk.adoc
@@ -145,7 +145,7 @@ used to track the allocated size of the list.
 Per entry, we find:
 
 `item` is the object provided upon which to base the object walk. Items in Git
-can be blobs, trees, commits, or tags. (See `Documentation/gittutorial-2.adoc`.)
+can be blobs, trees, commits, or tags. (See `Documentation/gitdatamodel.adoc`.)
 
 `name` is the object ID (OID) of the object - a hex string you may be familiar
 with from using Git to organize your source in the past. Check the tutorial
diff --git a/Documentation/git.adoc b/Documentation/git.adoc
index 6f0075f918..1f0cbaee7a 100644
--- a/Documentation/git.adoc
+++ b/Documentation/git.adoc
@@ -1200,7 +1200,7 @@ the Git Security mailing list <git-security@googlegroups.com>.
 
 SEE ALSO
 --------
-linkgit:gittutorial[7], linkgit:gittutorial-2[7],
+linkgit:gittutorial[7],
 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
 linkgit:gitglossary[7], linkgit:gitdatamodel[7],
 linkgit:gitcore-tutorial[7], linkgit:gitcli[7],
diff --git a/Documentation/gitcore-tutorial.adoc b/Documentation/gitcore-tutorial.adoc
index 2122aeb976..abbe193056 100644
--- a/Documentation/gitcore-tutorial.adoc
+++ b/Documentation/gitcore-tutorial.adoc
@@ -1649,7 +1649,6 @@ to follow, not easier.
 SEE ALSO
 --------
 linkgit:gittutorial[7],
-linkgit:gittutorial-2[7],
 linkgit:gitcvs-migration[7],
 linkgit:git-help[1],
 linkgit:giteveryday[7],
diff --git a/Documentation/gitcvs-migration.adoc b/Documentation/gitcvs-migration.adoc
index 905d08cd5f..66a5c3ed6d 100644
--- a/Documentation/gitcvs-migration.adoc
+++ b/Documentation/gitcvs-migration.adoc
@@ -194,7 +194,7 @@ repositories without the need for a central maintainer.
 SEE ALSO
 --------
 linkgit:gittutorial[7],
-linkgit:gittutorial-2[7],
+linkgit:gitdatamodel[7],
 linkgit:gitcore-tutorial[7],
 linkgit:gitglossary[7],
 linkgit:giteveryday[7],
diff --git a/Documentation/gitglossary.adoc b/Documentation/gitglossary.adoc
index b046d9cb29..6051f494d3 100644
--- a/Documentation/gitglossary.adoc
+++ b/Documentation/gitglossary.adoc
@@ -18,7 +18,6 @@ SEE ALSO
 --------
 linkgit:gitdatamodel[7],
 linkgit:gittutorial[7],
-linkgit:gittutorial-2[7],
 linkgit:gitcvs-migration[7],
 linkgit:giteveryday[7],
 link:user-manual.html[The Git User's Manual]
diff --git a/Documentation/gittutorial.adoc b/Documentation/gittutorial.adoc
index 519b8d8be2..006e534778 100644
--- a/Documentation/gittutorial.adoc
+++ b/Documentation/gittutorial.adoc
@@ -622,24 +622,12 @@ Next Steps
 ----------
 
 This tutorial should be enough to perform basic distributed revision
-control for your projects.  However, to fully understand the depth
-and power of Git you need to understand two simple ideas on which it
-is based:
+control for your projects.  However, to fully understand the Git
+documentation, it's useful to learn how Git stores the history of
+your project in its database. See linkgit:gitdatamodel[7] for an
+explanation.
 
-  * The object database is the rather elegant system used to
-    store the history of your project--files, directories, and
-    commits.
-
-  * The index file is a cache of the state of a directory tree,
-    used to create commits, check out working directories, and
-    hold the various trees involved in a merge.
-
-Part two of this tutorial explains the object
-database, the index file, and a few other odds and ends that you'll
-need to make the most of Git. You can find it at linkgit:gittutorial-2[7].
-
-If you don't want to continue with that right away, a few other
-digressions that may be interesting at this point are:
+A few other commands that may be interesting:
 
   * linkgit:git-format-patch[1], linkgit:git-am[1]: These convert
     series of git commits into emailed patches, and vice versa,
@@ -662,7 +650,6 @@ digressions that may be interesting at this point are:
 
 SEE ALSO
 --------
-linkgit:gittutorial-2[7],
 linkgit:gitcvs-migration[7],
 linkgit:gitcore-tutorial[7],
 linkgit:gitglossary[7],
diff --git a/command-list.txt b/command-list.txt
index 63ae2a67c9..5c649c882e 100644
--- a/command-list.txt
+++ b/command-list.txt
@@ -244,7 +244,6 @@ gitrepository-layout                    userinterfaces
 gitrevisions                            userinterfaces
 gitsubmodules                           guide
 gittutorial                             guide
-gittutorial-2                           guide
 gitweb                                  ancillaryinterrogators
 gitworkflows                            guide
 scalar                                  mainporcelain
-- 
gitgitgadget
Previous: Julia Evans via GitGitGadgetNext: Junio C Hamano
Message 40 of 42 in “[doc] Remove gittutorial-2”
  1. 0/3 [doc] Remove gittutorial-2Julia Evans via GitGitGadget, Sep 28, 2026
  2. 1/3 [doc] Remove gittutorial-2Julia Evans via GitGitGadget, Sep 28, 2026
  3. 2/3 [doc] Remove references to gittutorial-2Julia Evans via GitGitGadget, Sep 28, 2026
  4. 3/3 [doc] Delete translations of gittutorial-2 descriptionJulia Evans via GitGitGadget, Sep 28, 2026
  5. Junio C HamanoSep 29, 2026
  6. Julia EvansSep 29, 2026
  7. Julia EvansSep 29, 2026
  8. Junio C HamanoSep 30, 2026
  9. Julia EvansOct 1, 2026
  10. Junio C HamanoOct 2, 2026
  11. Junio C HamanoSep 29, 2026
  12. Junio C HamanoSep 29, 2026
  13. Tuomas AholaSep 30, 2026
  14. Junio C HamanoSep 30, 2026
  15. Julia EvansSep 30, 2026
  16. Kristoffer HaugsbakkSep 30, 2026
  17. Tuomas AholaSep 30, 2026
  18. Julia EvansSep 30, 2026
  19. 0/2 [doc] Remove gittutorial-2Julia Evans via GitGitGadget, Oct 5, 2026
  20. 1/2 doc: remove gittutorial-2Julia Evans via GitGitGadget, Oct 5, 2026
  21. Kristoffer HaugsbakkOct 5, 2026
  22. 2/2 doc: remove references to gittutorial-2Julia Evans via GitGitGadget, Oct 5, 2026
  23. Junio C HamanoOct 5, 2026
  24. Tuomas AholaOct 6, 2026
  25. Junio C HamanoOct 6, 2026
  26. Tuomas AholaOct 6, 2026
  27. Junio C HamanoOct 6, 2026
  28. Tuomas AholaNov 5, 2026
  29. Junio C HamanoNov 5, 2026
  30. Tuomas AholaNov 5, 2026
  31. Junio C HamanoNov 5, 2026
  32. Julia EvansOct 6, 2026
  33. Tuomas AholaOct 26, 2026
  34. Julia EvansOct 26, 2026
  35. Tuomas AholaOct 26, 2026
  36. Julia EvansOct 26, 2026
  37. Junio C HamanoOct 26, 2026
  38. 0/2 [doc] Remove gittutorial-2Julia Evans via GitGitGadget, Oct 26, 2026
  39. 1/2 doc: remove gittutorial-2Julia Evans via GitGitGadget, Oct 26, 2026
  40. 2/2 doc: remove references to gittutorial-2Julia Evans via GitGitGadget, Oct 26, 2026
  41. Junio C HamanoOct 26, 2026
  42. Junio C HamanoOct 26, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.