Junio C Hamano wrote: > Sounds like making "make test" build it is a more correct approach, > at least to me. What am I missing? How exactly? I'm not exactly competent in make, but this is what I understood from what you said (and it's obviously wrong): diff --git a/Makefile b/Makefile index 03524d0..da91937 100644 --- a/Makefile +++ b/Makefile @@ -580,6 +580,7 @@ TEST_PROGRAMS_NEED_X += test-svn-fe TEST_PROGRAMS_NEED_X += test-wildmatch TEST_PROGRAMS = $(patsubst %,%$X,$(TEST_PROGRAMS_NEED_X)) +TEST_PROGRAMS += git-remote-testpy # List built-in command $C whose implementation cmd_$C() is not in # builtin/$C.o but is linked in as part of some other command. -- 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