From: Junio C Hamano <gitster@pobox.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Jonathan Nieder <jrnieder@uchicago.edu>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH
Date: Sat, 28 Jun 2008 14:05:51 -0700 [thread overview]
Message-ID: <7vvdztmfrk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080628205817.GB3172@steel.home> (Alex Riesen's message of "Sat, 28 Jun 2008 22:58:17 +0200")
Alex Riesen <raa.lkml@gmail.com> writes:
> Jonathan Nieder, Fri, Jun 27, 2008 22:10:01 +0200:
>> --------
>> +[verse]
>> +'PATH=$(git --exec-path):$PATH'
>> '. git-parse-remote'
>
> You missed quoting. exec-path can contain whitespace.
Do you understand shell quoting rules?
$ foo='c d'
$ foo=$(echo a b):$foo
$ echo "$foo"
a b:c d
$ exit
> What do you need exec-path in PATH for?
When git-parse-remote is not installed in $(bindir) anymore, the shell
script library won't be found on user's $PATH in general.
next prev parent reply other threads:[~2008-06-28 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 20:10 [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH Jonathan Nieder
2008-06-28 20:58 ` Alex Riesen
2008-06-28 21:05 ` Junio C Hamano [this message]
2008-06-29 5:38 ` Jeff King
2008-06-29 16:10 ` jrnieder
2008-06-29 19:08 ` Junio C Hamano
2008-06-30 2:39 ` Jonathan Nieder
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=7vvdztmfrk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@uchicago.edu \
--cc=raa.lkml@gmail.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).