git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Kevin Ballard <kevin@sb.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git help broken
Date: Fri, 1 Aug 2008 16:41:21 +0200	[thread overview]
Message-ID: <20080801144121.GU32057@genesis.frugalware.org> (raw)
In-Reply-To: <200808010628.52875.chriscool@tuxfamily.org>

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

On Fri, Aug 01, 2008 at 06:28:52AM +0200, Christian Couder <chriscool@tuxfamily.org> wrote:
> I didn't realize that the function "is_git_command" would not work 
> for "help".

Is there any reason why help is not a builtin? I think that would solve
the problem.

I'm willing to do such a patch, I just asked in case that would be
no-go for some - for me - unknown reason.

Thanks.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-08-01 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 20:52 git help broken Kevin Ballard
2008-07-30 22:38 ` [PATCH] builtin-help: always load_command_list() in cmd_help() Miklos Vajna
2008-07-30 22:50   ` Kevin Ballard
2008-07-30 23:42 ` git help broken Johannes Schindelin
2008-07-30 23:44   ` Johannes Schindelin
2008-07-31  0:04     ` Miklos Vajna
2008-08-01  4:28       ` Christian Couder
2008-08-01 14:41         ` Miklos Vajna [this message]
2008-08-02  8:08           ` [PATCH] Builtin git-help Miklos Vajna
2008-08-21  2:51           ` git help broken Christian Couder
2008-08-21 14:21             ` [PATCH] Fix 'git help help' Miklos Vajna
2008-08-22  4:40               ` Christian Couder
2008-07-30 23:45   ` git help broken Kevin Ballard

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=20080801144121.GU32057@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=kevin@sb.org \
    /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).