Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs

From: Julia Evans <julia@jvns.ca>
Date: Oct 7, 2026, 12:13 UTC
Message-ID: <99bc9624-47a5-469d-bcae-8daa9b01581a@app.fastmail.com>
In-Reply-To: <ea29fe74-7f76-440c-9597-fdbc173be90f@app.fastmail.com>

> I recall only relatively recently learning that `-h` is not just a
> shorter way to type `--help`.

I just learned that recently too!

Show 8 quoted lines

> 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 <here> 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).

Show 12 quoted lines

>>
>>      * 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).