Lea Wiemann <lewiemann@xxxxxxxxx> writes: > Junio C Hamano wrote: >> I am guessing that the reason why you do not unset GIT_TEST_LONG upfront >> in the script is because the user can do: >> >> $ GIT_TEST_LONG=t; export GIT_TEST_LONG >> $ ./t9999-this-test.sh >> $ ./t9999-that-test.sh >> >> or even: >> >> $ GIT_TEST_LONG=t make test > > Yes, that's the idea. > >> If that is the case, however, I wonder if this --long-tests option is even >> necessary. > > It's very convenient for development, where you go back and forth > between "./t9503-gitweb-Mechanize.sh -v -l" and > "./t9503-gitweb-Mechanize.sh -v". All it takes is to add or remove > the "-l" at each invocation. So I think the switch is actually quite > useful. Heh, one-shot export "GIT_TEST_LONG_t ./t9999-this-test.sh" would equally be swift, but Ok. -- 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
