On Tue, Jul 17, 2012 at 8:31 PM, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > Nice, I thought about doing something like this myself but never had the time. Thanks. Took quite some time to take out the Git-specific functionality. And there's still a lot of room for improvement. > Perhaps to avoid duplication we could move to this and keep > Git-specific function in some other file. That would be fantastic! From a technical point of view, it would make a lot of sense to join forces here. How do you think would Sharness fit into the Git project? Is adding it as an external dependency an option? Let's share some ideas before getting to it. > Do you think that would be sensible, and would you be willing to > submit patches for that? While I haven't touched the names of the test functions, I renamed most of the global shell variables, e.g. GIT_TEST_OPTS to TEST_OPTS and TEST_DIRECTORY to SHARNESS_TEST_DIRECTORY. That might be a (minor) problem. As for the patches: absolutely. I'd really love to give something back to Git. -Mathias -- 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