On Fri, 2016-04-29 at 16:34 -0700, Stefan Beller wrote:
In upload-pack-2 we send each capability in its own packet buffer.
The construction of upload-pack-2 is a bit unfortunate as I would
like
it to not be depending on a symlink linking to upload-pack.c, but I
did
not find another easy way to do it. I would like it to generate
upload-pack-2.o from upload-pack.c but with '-DTRANSPORT_VERSION=2'
set.
Couldn't we check argv[0] and use that to determine protocol? Then we
could symlink executables rather than source code.