From: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Julia Evans <julia@jvns.ca>, Julia Evans <julia@jvns.ca>
Subject: [PATCH 2/3] [doc] Remove references to gittutorial-2
Date: Mon, 28 Sep 2026 20:25:21 +0000 [thread overview]
Message-ID: <a76819e3aff80b587156ba805fc6e93bb54cc41b.1790627122.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2241.git.1790627122.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 +++++------------------
6 files changed, 8 insertions(+), 23 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],
--
gitgitgadget
next prev parent reply other threads:[~2026-09-28 20:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:25 [PATCH 0/3] [doc] Remove gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 1/3] " Julia Evans via GitGitGadget
2026-09-28 20:25 ` Julia Evans via GitGitGadget [this message]
2026-09-28 20:25 ` [PATCH 3/3] [doc] Delete translations of gittutorial-2 description Julia Evans via GitGitGadget
2026-09-29 7:50 ` [PATCH 0/3] [doc] Remove gittutorial-2 Junio C Hamano
2026-09-29 10:42 ` Julia Evans
2026-09-29 11:09 ` Julia Evans
2026-09-30 7:50 ` Junio C Hamano
2026-10-01 22:21 ` Julia Evans
2026-10-02 7:38 ` Junio C Hamano
2026-09-29 21:58 ` Junio C Hamano
2026-09-29 22:24 ` Junio C Hamano
2026-09-30 6:15 ` Tuomas Ahola
2026-09-30 14:22 ` Junio C Hamano
2026-09-30 13:16 ` Julia Evans
2026-09-30 14:07 ` Kristoffer Haugsbakk
2026-09-30 6:00 ` Tuomas Ahola
2026-09-30 14:01 ` Julia Evans
2026-10-05 20:20 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-05 20:20 ` [PATCH v2 1/2] doc: remove gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` Kristoffer Haugsbakk
2026-10-05 20:20 ` [PATCH v2 2/2] doc: remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37 ` [PATCH v2 0/2] [doc] Remove gittutorial-2 Junio C Hamano
2026-10-06 5:50 ` Tuomas Ahola
2026-10-06 17:17 ` Junio C Hamano
2026-10-06 18:45 ` Tuomas Ahola
2026-10-06 20:48 ` Junio C Hamano
2026-10-06 17:34 ` Julia Evans
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a76819e3aff80b587156ba805fc6e93bb54cc41b.1790627122.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=julia@jvns.ca \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox