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

Ramifications of a git-sh-setup outside the PATH

From
Jonathan Nieder <jrnieder@uchicago.edu>
Date
Jun 27, 2008, 19:00 UTC
Message-ID
<20080627140027.BIA12244@m4500-01.uchicago.edu>
Hi gitsters,

I noticed in the release notes to Git 1.6.0 that dashed-form commands are moving to a libexecdir outside the PATH. I have been using Git with nd/dashless applied for about a month, and it does work well (thanks!). There was one little glitch: to use hg-fast-export.sh from fast-export.git (of repo.or.cz), I had to put git-sh-setup in the PATH.

I wanted to just change the ". git-sh-setup" line to ". git sh-setup", but of course that will not work. Am I missing something?

hg-fast-export uses git-sh-setup to handle --help, to provide the cd_to_toplevel function, and to set GIT_DIR. It would not take much work to avoid using git-sh-setup, although for my needs it was easier to put git-sh-setup in the PATH. But really, the use of git-sh-setup does not seem strange to me at all. Is use of git-sh-setup in scripts outside Git core discouraged?

The location of git-sh-setup was discussed before in the thread <http://thread.gmane.org/gmane.comp.version-control.git/33708>. Thanks for your time, and thank you for Git!

Sincerely, Jonathan

Next: Alex Riesen
Message 1 of 2 in “Ramifications of a git-sh-setup outside the PATH”
  1. Jonathan NiederJun 27, 2008
  2. Alex RiesenJun 28, 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.