git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 28, 2008, 21:05 UTC
Message-ID
<7vvdztmfrk.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080628205817.GB3172@steel.home>
Alex Riesen <raa.lkml@gmail.com> writes:
Show 7 quoted lines
> 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.

Previous: Alex RiesenNext: Jeff King
Message 3 of 7 in “Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH”
  1. Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATHJonathan Nieder, Jun 27, 2008
  2. Alex RiesenJun 28, 2008
  3. Junio C HamanoJun 28, 2008
  4. Jeff KingJun 29, 2008
  5. jrnieder@uchicago.eduJun 29, 2008
  6. Junio C HamanoJun 29, 2008
  7. Jonathan NiederJun 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.