summaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-08-18 20:46:58 (GMT)
committerJunio C Hamano <gitster@pobox.com>2014-09-15 20:23:28 (GMT)
commit20a7558f31e44e26ddbb8aa55bfd9316a6b67f82 (patch)
treecda6e1cd72ff5201be6613f89eb9ca34eca92c90 /Documentation/technical
parentd05b9618ce42e85936176537f939a4eb85d4d65e (diff)
downloadgit-20a7558f31e44e26ddbb8aa55bfd9316a6b67f82.zip
git-20a7558f31e44e26ddbb8aa55bfd9316a6b67f82.tar.gz
git-20a7558f31e44e26ddbb8aa55bfd9316a6b67f82.tar.bz2
send-pack: send feature request on push-cert packet
We would want to update the interim protocol so that we do not send the usual update commands when the push certificate feature is in use, as the same information is in the certificate. Once that happens, the push-cert packet may become the only protocol command, but then there is no packet to put the feature request behind, like we always did. As we have prepared the receiving end that understands the push-cert feature to accept the feature request on the first protocol packet (other than "shallow ", which was an unfortunate historical mistake that has to come before everything else), we can give the feature request on the push-cert packet instead of the first update protocol packet, in preparation for the next step to actually update to the final protocol. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/technical')
0 files changed, 0 insertions, 0 deletions