From: Zsolt Imre <imrexzsolt@gmail.com>
To: git@vger.kernel.org
Subject: Git Push Always uses Protocol Version 0
Date: Mon, 22 Jan 2024 08:59:35 +0000 [thread overview]
Message-ID: <FD545E92-18EF-44B5-A7D5-61ECADD880E6@gmail.com> (raw)
Hi there,
I'm not entirely sure if this is a bug or I am missing something, but I thought I would share in the hope someone can help out. I'm playing around with Git and trying to implement a git server that communicates over HTTP and supports Git protocol version 2 *only*.
When I `clone` a repository, the Git client (version 2.43.0), after fetching the capabilities using protocol version 2, it proceeds to fetch the refs, again, via protocol version 2 using the `ls-refs` command. However, when I try to `push` my changes to the repo, the Git client refuses to use protocol version 2 and tries to obtain the ref list using protocol version 0, even if I pass in the `-c protocol.version=2` command line argument.
Is there a way to make the client use only protocol version 2 instead of mixing the different protocols?
Thanks in advance for any help/guidance.
next reply other threads:[~2024-01-22 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 8:59 Zsolt Imre [this message]
2024-01-22 18:52 ` Git Push Always uses Protocol Version 0 Junio C Hamano
2024-01-22 19:24 ` Zsolt Imre
2024-01-22 22:04 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FD545E92-18EF-44B5-A7D5-61ECADD880E6@gmail.com \
--to=imrexzsolt@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).