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
Jonathan Nieder <jrnieder@uchicago.edu>
Date
Jun 30, 2008, 02:39 UTC
Message-ID
<Pine.GSO.4.62.0806292131390.28041@harper.uchicago.edu>
In-Reply-To
<7vbq1kawje.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
Show 11 quoted lines
> jrnieder@uchicago.edu writes:
>
>> [patch to use . "$(git --exec-path)/git-{parse-remote,sh-setup}"
>> instead of assuming they are in PATH]
>>
>> Junio: I stole the commit message from you. I hope you don't mind.
> 
> I don't, but reading the script again, I suspect it is not clear enough
> that the user is also responsible for setting up GIT_DIR appropriately
> before using it, perhaps by sourcing git-sh-setup.  We probably would want
> to add it in a separate patch.
Doesn't git-parse-remote.sh begin
	GIT_DIR=$(git rev-parse --git-dir 2>/dev/null) || :;

? And I don't imagine we want people to source git-sh-setup before sourcing git-sh-setup...

Confused, Jonathan

Previous: Junio C Hamano
Message 7 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.