git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Keith Thompson <Keith.S.Thompson@gmail.com>,  git@vger.kernel.org
Subject: Re: Bug report: Minor glitch in "git help" error message
Date: Fri, 18 Apr 2025 06:27:46 -0700	[thread overview]
Message-ID: <xmqqv7r1bnvx.fsf@gitster.g> (raw)
In-Reply-To: <20250418091612.GA10441@coredump.intra.peff.net> (Jeff King's message of "Fri, 18 Apr 2025 05:16:12 -0400")

Jeff King <peff@peff.net> writes:

> ...
> So probably a bad idea.
> ...
>
> The other thing it's tempting to do is teach "git help" to check ...
> ... We pick up
> third-party commands automatically by looking in the $PATH for them. But
> I don't think we can do the same for documentation ...

Great write-up.  Thanks.



      reply	other threads:[~2025-04-18 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 22:56 Bug report: Minor glitch in "git help" error message Keith Thompson
2025-04-18  1:24 ` Junio C Hamano
2025-04-18  3:52   ` Keith Thompson
2025-04-18  9:16     ` Jeff King
2025-04-18 13:27       ` Junio C Hamano [this message]

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=xmqqv7r1bnvx.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Keith.S.Thompson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).