Ramifications of a git-sh-setup outside the PATH

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <git@...>
Date: Friday, June 27, 2008 - 3:00 pm

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Ramifications of a git-sh-setup outside the PATH, Jonathan Nieder, (Fri Jun 27, 3:00 pm)
Re: Ramifications of a git-sh-setup outside the PATH, Alex Riesen, (Sat Jun 28, 8:01 am)