From: Christian Couder <chriscool@tuxfamily.org>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Kevin Ballard <kevin@sb.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Fix 'git help help'
Date: Fri, 22 Aug 2008 06:40:09 +0200 [thread overview]
Message-ID: <200808220640.10993.chriscool@tuxfamily.org> (raw)
In-Reply-To: <1219328508-11561-1-git-send-email-vmiklos@frugalware.org>
Le jeudi 21 août 2008, Miklos Vajna a écrit :
> git help foo invokes man git-foo if foo is a git command, otherwise it
> invokes man gitfoo. 'help' is not a git command, but the manual page is
> called git-help, so add this special exception.
>
> Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
Acked-by: Christian Couder <chriscool@tuxfamily.org>
> ---
>
> On Thu, Aug 21, 2008 at 04:51:11AM +0200, Christian Couder
<chriscool@tuxfamily.org> wrote:
> > But unfortunately it seems that your patch hasn't been merged into
> > master,
> > so "git help help" is still broken there and in git 1.6.0.
>
> Here is a patch for 'maint'.
It works fine.
Thanks,
Christian.
next prev parent reply other threads:[~2008-08-22 4:37 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
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 [this message]
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=200808220640.10993.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@sb.org \
--cc=vmiklos@frugalware.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).