Jeff King wrote:
On Mon, Dec 30, 2013 at 10:51:25AM -0800, Jonathan Nieder wrote:
These scratch areas for sub-tests should be under the t
trash directory, but because the TEST_OUTPUT_DIRECTORY
setting from the toplevel test leaks
[...]
This is not exactly true. The
Jonathan Nieder jrnie...@gmail.com writes:
Jeff King wrote:
On Mon, Dec 30, 2013 at 10:51:25AM -0800, Jonathan Nieder wrote:
These scratch areas for sub-tests should be under the t
trash directory, but because the TEST_OUTPUT_DIRECTORY
setting from the toplevel test leaks
On Mon, Dec 30, 2013 at 10:51:25AM -0800, Jonathan Nieder wrote:
I think it can be better, since the commit message left me scratching
my head while the patch itself seems pretty simple. How about
something like the following?
I am fine with that format, though...
Analysis and fix:
Jonathan Nieder jrnie...@gmail.com writes:
Jeff King wrote:
When I want to debug a failing test, I often end up doing:
cd t
./t4107-tab -v -i
cd tratab
The test names are long, so tab-completing on the trash directory is
very helpful. Lately I've noticed that there are a bunch of
Junio C Hamano wrote:
Jonathan Nieder jrnie...@gmail.com writes:
Jeff King wrote:
When I want to debug a failing test, I often end up doing:
cd t
./t4107-tab -v -i
cd tratab
The test names are long, so tab-completing on the trash directory is
very helpful. Lately I've noticed that
When I want to debug a failing test, I often end up doing:
cd t
./t4107-tab -v -i
cd tratab
The test names are long, so tab-completing on the trash directory is
very helpful. Lately I've noticed that there are a bunch of crufty trash
directories in my t/ directory, which makes my
Jeff King wrote:
When I want to debug a failing test, I often end up doing:
cd t
./t4107-tab -v -i
cd tratab
The test names are long, so tab-completing on the trash directory is
very helpful. Lately I've noticed that there are a bunch of crufty trash
directories in my t/ directory,
7 matches
Mail list logo