From: Junio C Hamano Date: Mon, 26 Oct 2026 22:36:12 GMT Subject: Re: [PATCH v3 2/2] doc: remove references to gittutorial-2 Message-ID: In-Reply-To: <0a42345cecec10bd32ae3db1a699452b164a2f25.1793022742.git.gitgitgadget@gmail.com> "Julia Evans via GitGitGadget" writes: Forgot to mention one more thing. > Documentation/gittutorial.adoc | 23 +++++------------------ > ... > 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. > ... > -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], As the main tutorial is being rewritten from scratch, and it seems to assume that nobody has ever heard of gittutorial-2 ;-), the above patch would not merge well when both topics meet in 'seen'. I do not think this topic to remove tutorial-2 would need further rework, but just in case if it ever becomes necessary, could you leave the changes out of this series? I can remember to take the other side and ignore the changes to the file done on this branch, but not having to remember one such thing helps quite a lot when you have to deal with 100+ merges to rebuild 'seen' on top of 'master', with updated topics of the day. Thanks.