> --- /dev/null > +++ b/t/lib-httpd/one-time-sed.sh > @@ -0,0 +1,16 @@ > +#!/bin/sh > + > +if [ -e one-time-sed ]; then > + "$GIT_EXEC_PATH/git-http-backend" >out > + > + sed "$(cat one-time-sed)" <out >out_modified > + > + if diff out out_modified >/dev/null; then > + cat out > + else > + cat out_modified > + rm one-time-sed > + fi > +else > + "$GIT_EXEC_PATH/git-http-backend" > +fi Add an explanatory comment somewhere (maybe, at the beginning), something like: If "one-time-sed" exists in $HTTPD_ROOT_PATH, run sed on the HTTP response, using the contents of "one-time-sed" as the sed command to be run. If the response was modified as a result, delete "one-time-sed" so that subsequent HTTP responses are no longer modified. This can be used to simulate the effects of the repository changing in between HTTP request-response pairs. > +test_expect_failure 'server is initially ahead - ref in want' ' [snip] > +test_expect_failure 'server is initially behind - ref in want' ' [snip] These are test_expect_failure, I assume because the fetch part has not been implemented yet. Can this be moved to the end of the patch set, once the fetch part has been implemented? There's also the case of when the server initially has a ref but later does not - can this be tested here too? The server part is already covered by the upload-pack test in which we craft a request with a non-existent ref, but it would be good to test the client part too.
