From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Devste Devste <devstemail@gmail.com>, git@vger.kernel.org
Subject: Re: Add warning when v0 protocol is used/downgraded
Date: Sun, 16 Jun 2024 18:19:19 -0700 [thread overview]
Message-ID: <xmqqjziobc2w.fsf@gitster.g> (raw)
In-Reply-To: <Zm8EqOfc_v4KBVVK@google.com> (Jonathan Nieder's message of "Sun, 16 Jun 2024 15:33:41 +0000")
Jonathan Nieder <jrnieder@gmail.com> writes:
> Specifying protocol version is meant to be backward compatible, and
> there are cases where the old protocol still needs to be used - for
> ...
> more so for protocol v2 for push, which doesn't exist yet - once it
> exists, it wouldn't be great if all pushes using existing servers
> produced an extra piece of noisy output. :)
I do not think it is a great idea to add this as a warning, as if
something bad is happening, either.
I also agree that it is a legitimate debugging issue. When the user
sees some symptom, after learning that the same symptom was reported
to be associated with the use of v2 on the Internet somewhere, it is
reasonable for the user to want to see what protocol is being used,
in order to debug the configuration, especially when the user thinks
they configured to use v0 (or vice versa)
So I am all for (1) adding to, if it is not already done, this kind
of information to the GIT_TRACE* output, and (2) advertising and
advocating GIT_TRACE* stuff as a useful debugging tool.
Thanks.
next prev parent reply other threads:[~2024-06-17 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 11:47 Add warning when v0 protocol is used/downgraded Devste Devste
2024-06-16 15:33 ` Jonathan Nieder
2024-06-17 1:19 ` Junio C Hamano [this message]
2024-06-18 18:24 ` Jeff King
2024-06-19 3:37 ` Devste Devste
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=xmqqjziobc2w.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=devstemail@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).