Re: t7005 and vi in GIT_EXEC_PATH

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Nov 10, 2007, at 5:09 PM, David Kastrup wrote:

Brian Gernhardt <benji@xxxxxxxxxxxxxxxxxx> writes:

If vi is in GIT_EXEC_PATH, then t7005-editor.sh fails because the real
vi is invoked instead of the test vi script.  This is because the git
wrapper puts GIT_EXEC_PATH ahead of ".".  I see no easy solution to
this problem, and thought I should bring it up with the list.

Putting "." at the front of GIT_EXEC_PATH instead of PATH would appear
to do the trick then, wouldn't it?

The GIT_EXEC_PATH I was referring to is the one set in the Makefile and compiled into git. The GIT_EXEC_PATH environment variable is set to the git repository. PATH ends up looking like this (paraphrased): "git.git:install directory:.:normal PATH". And since the install directory contains vi, the test fails (actually appears to hang because vi is waiting for input while it's output is being sent to / dev/null).

~~ Brian
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux