From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH] [doc] Use `man git` to teach users how to navigate the docs
Date: Mon, 28 Sep 2026 19:00:10 -0700 [thread overview]
Message-ID: <xmqqo6dgkead.fsf@gitster.g> (raw)
In-Reply-To: <CCB1855E-759F-4741-BE49-23FC6DD402A6@gmail.com> (Ben Knoble's message of "Mon, 28 Sep 2026 17:02:24 -0400")
Ben Knoble <ben.knoble@gmail.com> writes:
>> Mention `git help` instead of `giteveryday` for now, which does a better
>> job of giving an overview of everyday commands.
>
> [snip]
>
>> I thought about mentioning git help push and/or man git-push, but (from
>> a Mastodon survey I did) git push --help is the one users are most
>> familiar with, it's most similar to how other Unix tools work, and it
>> makes the description really clear and concise (-h for short help,
>> --help for long help).
> I appreciate the concision.
The survey result that says the users are more familiar with "git
cmd --help" merely tells us that they are not taking full advantage
of what they are offered ;-).
> I think “git help cmd” is quite a bit more
> useful than “git cmd --help” because the former supports
> aliases, HTML formats, and various other documents.
I agree that "git help cmd/concept/guide" is more useful for all
these reasons, with "git help help".
next prev parent reply other threads:[~2026-09-29 2:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:32 [PATCH] [doc] Use `man git` to teach users how to navigate the docs Julia Evans via GitGitGadget
2026-09-28 21:02 ` Ben Knoble
2026-09-29 2:00 ` Junio C Hamano [this message]
2026-09-29 11:29 ` Julia Evans
2026-09-29 19:51 ` Junio C Hamano
2026-09-29 21:00 ` Julia Evans
2026-09-29 21:20 ` Junio C Hamano
2026-10-06 20:06 ` [PATCH v2] doc: use " Julia Evans via GitGitGadget
2026-10-06 20:23 ` D. Ben Knoble
2026-10-07 6:06 ` Kristoffer Haugsbakk
2026-10-07 12:13 ` Julia Evans
2026-10-07 13:47 ` Junio C Hamano
2026-10-07 13:57 ` Julia Evans
2026-10-07 17:35 ` Junio C Hamano
2026-10-07 19:13 ` Junio C Hamano
2026-10-07 19:29 ` Julia Evans
2026-10-07 20:08 ` Junio C Hamano
2026-10-08 15:09 ` 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=xmqqo6dgkead.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=julia@jvns.ca \
--cc=kristofferhaugsbakk@fastmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.