summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-remote-explicit_remote-explicit
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2019-04-18 06:16:51 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-04-19 14:03:24 +0900
commitb7ce24d09526d4e181920ee029c25438196c2847 (patch)
tree2ae8b7a19cbc5dff59b42caad7e8807f941c7625 /t/t5515/fetch.br-remote-explicit_remote-explicit
parenttest-tool: handle the `-C <directory>` option just like `git` (diff)
downloadtgif-b7ce24d09526d4e181920ee029c25438196c2847.tar.xz
Turn `git serve` into a test helper
The `git serve` built-in was introduced in ed10cb952d31 (serve: introduce git-serve, 2018-03-15) as a backend to serve Git protocol v2, probably originally intended to be spawned by `git upload-pack`. However, in the version that the protocol v2 patches made it into core Git, `git upload-pack` calls the `serve()` function directly instead of spawning `git serve`; The only reason in life for `git serve` to survive as a built-in command is to provide a way to test the protocol v2 functionality. Meaning that it does not even have to be a built-in that is installed with end-user facing Git installations, but it can be a test helper instead. Let's make it so. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-remote-explicit_remote-explicit')
0 files changed, 0 insertions, 0 deletions