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

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, 19:29 UTC
Message-ID
<3a665230-b221-410b-9a58-96c01210aea0@app.fastmail.com>
In-Reply-To
<xmqqfqyh728j.fsf@gitster.g>
On Wed, Oct 7, 2026, at 3:13 PM, Junio C Hamano wrote:
Show 26 quoted lines
> "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> From: Julia Evans <julia@jvns.ca>
>>
>> Many existing users of Git don't know how Git's documentation is
>> structured, and a lot of folks have expressed frustration that `man git`
>> doesn't make it easy to find out how to get help with using Git.
>>
>> Explain how Git's help system works in `man git`
>> (`git push -h` gives a short help, `git push --help` is the full docs),
>> since it's a slightly unusual approach.
>>
>> Remove the references to gittutorial and giteveryday since they're
>> unlikely to help new users learn Git. Currently they feel very
>> aspirational (it would be nice to have a tutorial and a guide to
>> everyday Git commands!), but we should give users a realistic view of
>> what the documentation actually provides.
>
> The text mentions removing 'tutorial' and 'everyday', but does
> not explain why we no longer reference 'user-manual', 'datamodel',
> and 'cli'.  The third iteration should justify this.  At least,
> I recall that adding a reference to 'cli' early in the document was
> a deliberate decision, and we should explain why it is no longer
> relevant.  It would not be surprising if it has become obsolete
> over the last decade, but we still need to spell out why it is no
> longer appropriate to reference here.
Thanks, can do. Here's my thought process:
- Removed 'cli' because (from my perspective as a user) it seems like
  something that's written for Git developers and not users, like
  with "Commands that support the enhanced option parser",
  how is a user supposed to know which commands support
  the enhanced parser? I think it makes sense as a guide to
  scripting Git but not for interactive use. Some of the bits on `diff`
  feel like they might belong in the `git diff` man page, not sure.
- Removed "user-manual" because it's outdated. The chapter on
  "Sharing development with others" explains how to use
  `git format-patch` which is not how most people collaborate with
  git.
- Once all the others were removed it seemed a bit out of place
  to mention `gitdatamodel`.
Previous: Junio C HamanoNext: Junio C Hamano
Message 16 of 18 in “[doc] Use `man git` to teach users how to navigate the docs”
  1. [doc] Use `man git` to teach users how to navigate the docsJulia Evans via GitGitGadget, Sep 28, 2026
  2. Ben KnobleSep 28, 2026
  3. Junio C HamanoSep 29, 2026
  4. Julia EvansSep 29, 2026
  5. Junio C HamanoSep 29, 2026
  6. Julia EvansSep 29, 2026
  7. Junio C HamanoSep 29, 2026
  8. doc: use `man git` to teach users how to navigate the docsJulia Evans via GitGitGadget, Oct 6, 2026
  9. D. Ben KnobleOct 6, 2026
  10. Kristoffer HaugsbakkOct 7, 2026
  11. Julia EvansOct 7, 2026
  12. Junio C HamanoOct 7, 2026
  13. Julia EvansOct 7, 2026
  14. Junio C HamanoOct 7, 2026
  15. Junio C HamanoOct 7, 2026
  16. Julia EvansOct 7, 2026
  17. Junio C HamanoOct 7, 2026
  18. Julia EvansOct 8, 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.