On Mon, Jan 26, 2009 at 12:06:08PM +0100, Johannes Schindelin wrote: > So maybe I was wrong to assume that this is cvsserver specific, but then, > you made that mistake rather easy to make. Yes, in retrospect I probably should have split off patches 6, 7, 8, and maybe 5 (5-7 fix issues that patch 8 exposes in the test suite) into a separate patch series. When or if a v2 is needed, should I split them off then? > > 4. The test-bin-wrapper.sh script does not actually need to set > > environment variables (GIT_EXEC_DIT and templates) for purposes > > of this patch. But my thought was that in this form you could > > run things straight out of the test-bin directory to manually try > > out new code without needing to actually install a build or mess > > with the environment variables yourself. It could also be > > extended to handle other global wrapper needs relatively easily, > > such as valgrind. > > Umm. > > You missed the valgrind patch series. Actually, I'm (poorly) alluding to some comments in the original patch 8 email, where I pointed out an expected conflict with the valgrind patches. To briefly recap, there are at least 3 possible strategies of resolving such a conflict, and I'm not sure which makes the most sense: Keep valgrind design, and extend it with limited bindir support. Keep limited bindir design and extend it with valgrind support. Or keep both, and have the runtime setup logic make them mutually exclusive. -- Matthew Ogilvie [mmogilvi_git@xxxxxxxxxxxx] -- 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
