git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, David Kastrup <dak@gnu.org>
Subject: Re: [PATCH 0/3] git-help -i (info): finishing touches
Date: Mon, 10 Dec 2007 21:27:26 -0800	[thread overview]
Message-ID: <7vprxdhkch.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200712110622.51583.chriscool@tuxfamily.org> (Christian Couder's message of "Tue, 11 Dec 2007 06:22:51 +0100")

Christian Couder <chriscool@tuxfamily.org> writes:

> Le lundi 10 décembre 2007, Junio C Hamano a écrit :
>> Junio C Hamano <gitster@pobox.com> writes:
>> > This series attempts to add finishing touches to "git help -i" (info)
>> > support.
>
> It looks like the patch series you talk about was not sent to the list.

Hmph, it appears that there was a misconfiguration on my part to drive
send-email.  Look into 'next' branch.

> In the last patch there is:
>
> diff --git a/help.c b/help.c
> index 9d7ad6f..c96b167 100644
> --- a/help.c
> +++ b/help.c
> @@ -286,6 +286,7 @@ static void show_man_page(const char *git_cmd)
>  static void show_info_page(const char *git_cmd)
>  {
>         const char *page = cmd_to_page(git_cmd);
> +       setenv("INFOPATH", GIT_INFO_PATH, 1);
>         execlp("info", "info", "gitman", page, NULL);
>  }
>
> But I wonder if something like this would be better:

I do not think so, as MANPATH has that funky semantics of "appending the
system path where a single colon separates an empty path component from
the rest." but I do not think there is anything like that in INFOPATH.

      reply	other threads:[~2007-12-11  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1197279969-10613-1-git-send-email-gitster@pobox.com>
2007-12-10 10:06 ` [PATCH 0/3] git-help -i (info): finishing touches Junio C Hamano
2007-12-11  5:22   ` Christian Couder
2007-12-11  5: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=7vprxdhkch.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=chriscool@tuxfamily.org \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.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).