From: Junio C Hamano <gitster@pobox.com>
To: kristofferhaugsbakk@fastmail.com
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>
Subject: Re: [PATCH] branch: advice using git-help(1) instead of man(1)
Date: Fri, 28 Nov 2025 08:40:59 -0800 [thread overview]
Message-ID: <xmqq345yjejo.fsf@gitster.g> (raw)
In-Reply-To: <advice_git-help.64@msgid.xyz> (kristofferhaugsbakk@fastmail.com's message of "Fri, 28 Nov 2025 13:54:29 +0100")
kristofferhaugsbakk@fastmail.com writes:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> 8fbd903e (branch: advise about ref syntax rules, 2024-03-05) added
> an advice about checking git-check-ref-format(1) for the ref syntax
> rules. The advice uses man(1). It’s better to use Git’s own git-help(1)
> instead of an external command.
Substatiate "better" a bit better? If there were a universal help
facility, we wouldn't have had to invent our own, and that would
have been even better, but since we do not live in such an ideal
world, we cater to people who live in a man-less land by having our
own.
In other words, "An external command" is not the issue. Some people
living in a man-less land is.
... for the ref syntax rules and refers to the man(1) command,
which may not be available on some platforms. Refer to 'git
help' instead.
> Also change to using single quotes (') to quote the command since that
> is more conventional.
Yup. We haven't added markdown or asciidoc interpreter to our
advise() machinery ;-)
next prev parent reply other threads:[~2025-11-28 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 12:54 [PATCH] branch: advice using git-help(1) instead of man(1) kristofferhaugsbakk
2025-11-28 16:40 ` Junio C Hamano [this message]
2025-11-29 1:56 ` Junio C Hamano
2025-12-02 15:28 ` Kristoffer Haugsbakk
2025-12-02 15:56 ` [PATCH v2] " kristofferhaugsbakk
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=xmqq345yjejo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).