SZEDER Gábor <szeder@xxxxxxxxxx> writes: > You can have a look at these patches at > > https://github.com/szeder/git completion-test-multiple-bash-versions > > and perhaps you could even adapt it to LFS and/or p4 somehow. > >> Plus if we want to be consistent we would >> need to do the same for LFS 1.0, 1.2, and for pretty much every other >> dependency... > > I'm not sure we should be consistent in this case, at least not solely > for consistency's sake and not in git.git. Taking what I did for Bash > and doing it for different versions of LFS, p4, etc. could perhaps > keep the runtime under control, but t/Makefile would surely get out > of control rather quickly. Putting these into a travis-ci matrix is > so much simpler, but the runtime makes it infeasible, of course. I took a brief look of your branch, and I like its approach. If I understood your approach correctly, you: * Group selected tests in t/ as "these are bash related tests I care about" in t/Makefile; * Add Travis test target to build Git with specific versions of bash, and run the above target instead of the full test to exercise the version of bash you are testing. And I agree that the same can be done for LFS versions and P4 versions. Only a handful tests in t/ are about these niches. > I think the best we can do is to keep this out of git.git and let > (hope?) developers interested in a particular subsystem do this > "multiple version compatibility" tests as they see fit. -- 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