Felipe Contreras <felipe.contre...@gmail.com> writes:
> This only makes sense for the python remote helpers framework.
A better explanation is sorely needed for this. If the test were
feeding python snippet to be sourced by python remote helper to be
tested, the new remote-testgit.bash would not have any hope (nor
need) to grok it, and "this only makes sense for python" makes
perfect sense and clear enough, but that is not the case.
If the justification were like this:
remote-testgit: remove non-local tests
The simplified remote-testgit does not talk with any remote
repository and incapable of running non-local tests. Remove
them.
I would understand it, and I wouldn't say it is a regression in the
test not to test "non-local", as that is not essential aspect of
these tests (we are only interested in testing the object/ref
transfer over remote-helper interface and do not care what the
"other side" really is).
But I am not quite sure what you really mean by "non-local"
functionality in the first place. The original test weren't opening
network port to emulate multi-host remote transfer, were it?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
