From: Julia Evans Date: Wed, 07 Oct 2026 12:13:22 GMT Subject: Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs Message-ID: <99bc9624-47a5-469d-bcae-8daa9b01581a@app.fastmail.com> In-Reply-To: > I recall only relatively recently learning that `-h` is not just a > shorter way to type `--help`. I just learned that recently too! > Okay, so now we don’t have to list out every guide that might be of > interest. That’s cool. > > I see that this would conflict with my topic > kh/doc-gitbreaking-changes7.[1] Just would since my topic hasn’t > been integrated yet (RFC). I use the old style of mentioning the > new gitbreaking-changes(7) (“see for ...”. I will remove > that change in order to stay consistent with this topic. > 🔗 1: https://lore.kernel.org/git/CV_gitbrchanges7_please.d1c@m5gid.xyz/ That makes sense to me, thanks! I saw that topic and funnily I've been working on moving most of the content of `gitworkflows` in the other direction (from the user facing manual pages to the internal-only docs). >> >> * mention the git help push form too >> * mention you can get HTML docs with git help --web push at the end to >> advertise git help's great features, and remove >> https://git.github.io/htmldocs/git.html since >> https://git-scm.com/docs has a nicer view and 3 different options is >> a lot. > > Nitpick: Okay, but with the current commit message I don’t really > understand why the git.github.io link is gone. I have to guess that it > is an effective duplicate of git-scm or something since git-scm does > remain after this change. Yep! It has the same content as https://git-scm.com as far as I know, but without a lot of the nice features (a table of contents, an overview of all the documentation, search, etc).